Skip to main content
Glama

The Doll Scout Home Tools

Plan paper or media use · Rocketbook Mini - Next Gen

tds_purchase_m_rocketbook_new_rocketbook_mini
Read-onlyIdempotent

Recorded model Mini - Next Gen. 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_new_rocketbook_mini"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYes
monthlyUseYes
unitsOnHandYes
offeredModelYes
unitsPerPackYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/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 elsewhere. The description adds nothing behavioral beyond that — it does not say the tool returns a purchase plan or computed quantity, what it does with unitsOnHand, or how months interacts with monthlyUse. "Confirm the exact type, dimensions and compatibility" reads as advice to the user rather than a disclosure of tool behavior.

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

Conciseness2/5

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

The text is short, but brevity here is under-specification rather than economy. The lead sentence is a near-meaningless product restatement, and the remaining sentences are fragmentary advisories that never establish what the tool produces, so the front-loaded content does not orient the reader.

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?

With five required, entirely undocumented parameters, no output schema, and no sibling differentiation, the description should explain the computation and the unit relationships. Instead it supplies only product-name guidance and a generic compatibility reminder, leaving an agent unable to confidently construct a valid call or predict the result.

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 0% across five required parameters, so the description must carry the load and it only partly does: it maps "seller's model field or exact variant name" to offeredModel and implies unit consistency for monthlyUse/unitsOnHand/unitsPerPack. It says nothing about what months means (planning horizon bounds 1-120), whether monthlyUse is per month per unit or per pack, or how unitsPerPack converts to unitsOnHand. Some meaning is added, but three of five parameters remain opaque.

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 opens with "Recorded model Mini - Next Gen," which restates the product name already present in the title and tool name rather than stating what the tool does. It never says the tool computes a purchase/usage plan from usage rates, stock on hand, and pack sizes, so the agent must infer the operation entirely from the parameter list. The only differentiator from the many sibling product tools is the embedded product name, not a described action.

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?

"Use the seller's model field or exact variant name" gives a hint about how to populate offeredModel, and "Use the same measured unit for your task and the package" implies unit consistency. However, there is no guidance on when to choose this tool versus siblings such as tds_quote_framing_plan or the other Rocketbook variants, and no prerequisites or exclusions are stated.

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.