Skip to main content
Glama

The Doll Scout Home Tools

Plan paper or media use · Rocketbook Beacons

tds_purchase_m_rocketbook_rocketbook_beacons
Read-onlyIdempotent

Recorded model Beacons. 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_beacons"
  }
}

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 establish that this is a read-only, idempotent, non-open-world operation. The description adds little beyond vague input advice; it does not explain what the tool returns, how quantities are planned, or any behavioral constraints beyond 'Confirm the exact type, dimensions and compatibility.'

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 but poorly front-loaded: the first sentence is an unclear fragment, and the remaining sentences are disjointed input notes. It is not verbose, but the structure does not help an agent quickly grasp the tool’s purpose.

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-parameter planning tool with no output schema and no schema descriptions, the definition is too thin. It does not explain how the parameters combine to produce a result or what the agent should expect from the call.

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%, so the description must carry parameter meaning. It only loosely addresses offeredModel and unit consistency, and leaves monthlyUse, months, unitsOnHand, and unitsPerPack undefined. The required integer bounds are left entirely to the schema.

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 Beacons,' which does not state a clear action or explain what the tool computes. It reads more like an input-format note than a purpose statement, and it does not distinguish this planning tool from sibling purchase-planning tools.

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 explicit guidance on when to use this tool versus alternatives. The sentences about using the seller's model field, keeping units consistent, and confirming compatibility are input cautions rather than usage context or exclusions.

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.