caravan_price_historyCompare privacy-safe historical discounts before deciding whether to join a pool. EXPERIMENTAL — TEST NETWORK ONLY — NOT A FINANCIAL PRODUCT OR SERVICE — NO REAL FUNDS — AS IS, NO WARRANTY, NO LIABILITY — USE AT YOUR OWN RISK
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| cursor | No | ||
| productId | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds important caveats about being experimental, test-network-only, and not involving real funds, which improves transparency beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and front-loaded with the main purpose. The disclaimers are necessary given the tool's experimental and non-financial nature, and there is no superfluous content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the overall purpose and important warnings, but omits parameter semantics and any indication of the output shape. Since there is no output schema, these omissions leave the agent with meaningful gaps in understanding how to call and interpret the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
None of the three parameters (productId, limit, cursor) are described in the schema or the description. The agent cannot reliably infer their meaning or formatting, especially the pagination semantics of limit and cursor.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the action ('compare historical discounts') and the resource ('clearing-price history'), with a use context ('before deciding whether to join a pool'). It does not explicitly contrast with sibling tools, but the purpose is distinct enough to avoid confusion.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives useful context about when to use the tool: before deciding whether to join a pool. However, it does not explicitly mention alternatives or state when not to use this tool, leaving some implicit inference to the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct purpose: posting intents/offers, committing, checking pools, polling match status, paying/revealing, attesting, and seller onboarding. No two tools overlap in functionality, and even similar-sounding ones (check_pools vs. get_match_status) target different objects (pools vs. intents).
All tools follow the same caravan_verb_noun pattern with snake_case, making the naming fully consistent and predictable. The prefix also clearly ties tools to the server.
With 9 tools, the set is well-scoped for a marketplace/aggregation service. It covers the core workflow without being sparse or overwhelming, fitting the recommended 3-15 range.
The tools cover the main lifecycle: posting intents and offers, committing, matching, payment, attestation, and seller onboarding. However, there is no explicit cancel/withdraw tool for intents or offers, which is a minor gap in full lifecycle management.