Skip to main content
Glama

The Doll Scout Home Tools

Plan paper or media use · Rocketbook Fusion

tds_purchase_m_rocketbook_rocketbook_fusion
Read-onlyIdempotent

Recorded model Fusion. 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_rocketbook_fusion"
  }
}

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say what happens on model mismatch or unit inconsistency, whether errors are raised, or what the response contains. "Confirm the exact type, dimensions and compatibility" hints at validation but never states behavior.

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 description is short and wastes no space, but it is fragmented into imperatives with no leading statement of purpose, and the opening sentence is pure noise. Brevity here reflects under-specification rather than efficient structure.

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?

Five required parameters, zero schema coverage and no output schema mean the description must explain both the computation and the expected result. It instead offers generic matching advice, leaving the agent unable to predict what the tool computes or returns — inadequate for a parameterized purchase-planning calculator.

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% across five required parameters, so the description must carry the burden. It clarifies only offeredModel (use the seller's model field or exact variant name) and indirectly the unit consistency between monthlyUse and unitsPerPack. It says nothing about the meaning, bounds, or units of months, unitsOnHand, or unitsPerPack, and never defines the measured unit itself.

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 first sentence, "Recorded model Fusion," merely restates the tool name and title. The remainder is parameter hygiene advice ("Use the seller's model field...", "Confirm the exact type, dimensions and compatibility") and never states the actual operation — presumably computing how many packs are needed from monthly use, months, and units on hand. An agent cannot tell from this text what the tool produces.

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?

There is guidance on how to fill offeredModel (seller's model field or exact variant name), but no statement of when to use this tool versus the many sibling Rocketbook product tools, nor any prerequisite or exclusion. The agent must infer selection from the name alone.

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.