Bug Fix - OpenRouter MCP Server Schema Validation Erro

[michelle0927]

Resolves #17097

The documentation shows that model is required, and models is optional. I think the problem was that we had both model and models props required.

Summary by CodeRabbit

• Chores
  • Updated action versions for "Send Chat Completion Request" and "Send Completion Request".
  • Made the "models" property optional in both actions and refined its description.
  • Bumped the package version to 0.1.1.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
docs-v2	⬜️ Ignored (Inspect)			Jun 19, 2025 8:26pm
pipedream-docs	⬜️ Ignored (Inspect)			Jun 19, 2025 8:26pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Jun 19, 2025 8:26pm

[coderabbitai]

Walkthrough

The version numbers for two OpenRouter action modules and the package were incremented. The models property in both action modules was updated to be optional and its description was slightly modified. No functional or control flow changes were made, and the schema for models remains present.

Changes

File(s)	Change Summary
components/openrouter/actions/send-chat-completion-request/send-chat-completion-request.mjs, components/openrouter/actions/send-completion-request/send-completion-request.mjs	Incremented action version to "0.0.2", made models prop optional, and removed trailing period from its description.
components/openrouter/package.json	Incremented package version from "0.1.0" to "0.1.1".

Assessment against linked issues

Objective	Addressed	Explanation
Update schema to expect model (string) instead of models (array) in affected functions (#17097)	❌	The changes only made models optional and updated its description; model was not introduced.
Align schema with OpenRouter's API specification for chat and completion requests (#17097)	❌	The schema still includes models (now optional), not the required singular model property.

Assessment against linked issues: Out-of-scope changes

Code Change	Explanation
Incremented package version in package.json (components/openrouter/package.json)	This change is unrelated to the schema validation bug and is not required for the stated fix.

Poem

A bunny hopped through versioned fields,
Making models optional, as the spec yields.
But singular model still out of sight,
Schema’s not fixed—try as it might!
With every hop, a lesson learned:
Bugs need more than versions turned.
🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

components/openrouter/actions/send-chat-completion-request/send-chat-completion-request.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:201:49)

components/openrouter/actions/send-completion-request/send-completion-request.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:201:49)

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

components/openrouter/actions/send-chat-completion-request/send-chat-completion-request.mjs (1)

158-158: Consider handling undefined models value.

Since models is now optional, this.models could be undefined. While this may work fine if the OpenRouter API handles undefined values gracefully, consider conditionally including the property to avoid sending undefined values:

-      models: this.models,
+      ...(this.models && { models: this.models }),

components/openrouter/actions/send-completion-request/send-completion-request.mjs (1)

157-157: Consider handling undefined models value.

Since models is now optional, this.models could be undefined. While this may work fine if the OpenRouter API handles undefined values gracefully, consider conditionally including the property to avoid sending undefined values:

-      models: this.models,
+      ...(this.models && { models: this.models }),

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e8f4744 and 3c6a1a3.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (3)

• components/openrouter/actions/send-chat-completion-request/send-chat-completion-request.mjs (2 hunks)
• components/openrouter/actions/send-completion-request/send-completion-request.mjs (2 hunks)
• components/openrouter/package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: pnpm publish
• GitHub Check: Lint Code Base
• GitHub Check: Publish TypeScript components
• GitHub Check: Verify TypeScript components

🔇 Additional comments (5)

components/openrouter/package.json (1)

3-3: LGTM! Appropriate version increment for bug fix.

The patch version increment from 0.1.0 to 0.1.1 correctly follows semantic versioning for this bug fix addressing schema validation errors.

components/openrouter/actions/send-chat-completion-request/send-chat-completion-request.mjs (2)

8-8: LGTM! Appropriate version increment.

The patch version increment correctly reflects the bug fix changes made to the schema validation.

---

109-110: LGTM! Correctly addresses the schema validation issue.

Making the models property optional resolves the reported issue where both model and models were incorrectly required. This change aligns the implementation with the documented behavior where only model is required.

components/openrouter/actions/send-completion-request/send-completion-request.mjs (2)

7-7: LGTM! Appropriate version increment.

The patch version increment correctly reflects the bug fix changes made to the schema validation.

---

108-109: LGTM! Correctly addresses the schema validation issue.

Making the models property optional resolves the reported issue where both model and models were incorrectly required. This change aligns the implementation with the documented behavior where only model is required.

[luancazarine]

Hi @michelle0927, LGTM! Ready for QA!