Skip to main content
Glama

The Doll Scout Home Tools

Plan paper or media use · Rocketbook Rocketplanner Desk Calendar

tds_purchase_m_rocketbook_rocketplanner_calendar
Read-onlyIdempotent

Recorded model Rocketplanner Desk Calendar. Use the seller’s model field or exact variant name. Use the same measured unit for your task and the package. Confirm the exact type, dimensions and compatibility.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "offeredModel": "<offeredModel>",
      "monthlyUse": "<monthlyUse>",
      "months": "<months>",
      "unitsOnHand": "<unitsOnHand>",
      "unitsPerPack": "<unitsPerPack>"
    },
    "name": "tds_purchase_m_rocketbook_rocketplanner_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYes
monthlyUseYes
unitsOnHandYes
offeredModelYes
unitsPerPackYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds only input consistency and compatibility confirmation, not how the computation works, what assumptions it makes about usage over months, or what it returns. It adds minimal behavioral context 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.

Conciseness3/5

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

The definition is short and free of obvious padding, but the first sentence ('Recorded model Rocketplanner Desk Calendar') is awkward and does not front-load the actual purpose. The remaining sentences are generic input guidance rather than a structured explanation of the tool.

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

Completeness2/5

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

For a five-required-parameter planning calculator with no schema property descriptions and no output schema, the description is far too thin. It omits what the computation does, what each parameter means, and what assumptions (constant monthly use, unit matching) drive the result, leaving an agent unable to invoke it confidently.

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

Parameters2/5

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

Schema description coverage is 0% for all five parameters. The description clarifies offeredModel ('seller’s model field or exact variant name') and hints at unit consistency, but it never explains monthlyUse, months, unitsOnHand, or unitsPerPack. It does not compensate for the empty schema documentation.

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

Purpose2/5

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

The description names the product model but never states the action: it does not say this tool calculates required packs, plans usage, or computes anything. The title supplies 'Plan paper or media use', but the description itself is essentially a model name plus input advice, leaving the core purpose vague.

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

Usage Guidelines2/5

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

It gives input-format advice ('Use the seller’s model field or exact variant name', 'Use the same measured unit') but no guidance on when to choose this tool versus other Rocketbook models or planning tools. There is no when-to-use, when-not-to-use, or alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.