Skip to main content
Glama

The Doll Scout Home Tools

Plan paper or media use · Rocketbook Fusion Plus

tds_purchase_m_rocketbook_fusion_plus_1
Read-onlyIdempotent

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

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds only a vague unit-consistency rule and an instruction to "confirm the exact type, dimensions and compatibility"; it says nothing about how the calculation is performed, rounding, or whether surplus stock is netted against on-hand units.

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?

Three short sentences, so it is not bloated, but the opening "Recorded model Fusion Plus" is noise that occupies the front-loaded position where the purpose should be. The remaining sentences are compact but read as a checklist rather than a coherent definition.

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?

This is a five-required-parameter calculation tool with no output schema and no parameter descriptions, and the description supplies neither the computation semantics nor per-parameter meaning. An agent would have to guess how unitsOnHand and unitsPerPack interact with months and monthlyUse.

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 compensate and largely fails. It touches offeredModel (seller's model field / exact variant name) and implies monthlyUse, unitsOnHand and unitsPerPack share a unit, but never explains the unit's meaning (sheets per month? packs?) or says anything about the months parameter.

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 never states what the tool actually does. "Recorded model Fusion Plus" is opaque, and nothing indicates this is a consumption/repurchase planner that computes packs needed from monthlyUse, months, unitsOnHand and unitsPerPack. Only the title hints at planning paper use.

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 no when-to-use guidance and no named alternative among the many sibling purchase planners (e.g. tds_quote_framing_plan or other Rocketbook variants). "Use the seller's model field or exact variant name" is parameter advice, not tool-selection guidance.

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.