RocketVault Public Knowledge and Marketplace

Compare RocketVault plans

compare_plans

Read-only

Return current RocketVault prices, card limits, trial length, and eBay capability availability from the canonical pricing configuration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "compare_plans"
  }
}

Input Schema

Name	Required	Description	Default
`capability`	No	Optionally identify plans that include an eBay capability.	all

Output Schema

Name	Required	Description	Default
`plans`	Yes
`source_url`	Yes
`free_trial_days`	Yes
`eligible_plan_ids`	Yes
`facts_verified_at`	Yes
`requested_capability`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish that this is a safe, read-only, non-destructive, closed-world operation. The description adds that the data comes from the canonical pricing configuration and that values are current, but it does not disclose other behavioral details such as caching or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single well-structured sentence with no wasted wording. The key returned data is front-loaded and immediately useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool with a complete input schema, explicit annotations, and an output schema, the description provides enough context to understand the purpose and data source. It is only slightly incomplete because it does not clarify how the capability filter changes the comparison.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the single optional enum parameter is fully documented in the schema. The description only indirectly relates to it by mentioning eBay capability availability, so it does not add meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: it returns RocketVault pricing, card limits, trial length, and eBay capability availability. The purpose is clear, but it does not explicitly differentiate itself from the listed sibling tools, which focus on fetching and marketplace search operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the tool name and the data it returns, but the description provides no explicit when-to-use or when-not-to-use guidance. It also does not mention alternatives such as fetch for other RocketVault data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All RocketVault Public Knowledge and Marketplace tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?