Skip to main content
Glama

The Doll Scout Home Tools

Plan paper or media use · Rocketbook Flip - Next Gen

tds_purchase_m_rocketbook_new_rocketbook_flip
Read-onlyIdempotent

Recorded model Flip - 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_flip"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYes
monthlyUseYes
unitsOnHandYes
offeredModelYes
unitsPerPackYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior3/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 one genuinely relevant behavioral constraint — keep measurement units consistent between the task and the package — but says nothing about how the calculation is performed or what happens when inputs are inconsistent (e.g. mismatch of unitsOnHand vs unitsPerPack).

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?

Short and readable, but the opening sentence is a wasted product-name restatement and "Confirm the exact type, dimensions and compatibility" is generic boilerplate that does not tell the agent how to act. The useful unit-consistency rule is buried rather than front-loaded.

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?

A five-parameter, all-required computational tool with no output schema and no parameter descriptions needs the description to explain inputs and the resulting quantity; instead it offers only a variant-name hint and a unit warning. An agent could invoke it but could easily mis-scale monthlyUse versus pack size without further explanation.

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 load. It only loosely gestures at offeredModel ("seller's model field or exact variant name") and at the unit-consistency relationship between monthlyUse, unitsPerPack and unitsOnHand; the months parameter is never mentioned and no parameter's format or expected value is clarified.

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 Flip - Next Gen", simply restates the product variant already encoded in the tool name and title; no verb states what the tool actually does (presumably compute a purchase quantity from monthly use, months, pack size and stock). Nothing distinguishes it from sibling Rocketbook model tools beyond the product name.

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-selection advice ("Use the seller's model field or exact variant name", "Confirm the exact type, dimensions and compatibility") but no when-to-use or when-not-to-use guidance, and no routing among the many sibling purchase_* tools. A user still cannot tell from this text why they would pick this tool over another Rocketbook variant entry.

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.