Skip to main content
Glama

The Doll Scout Home Tools

Plan paper or media use · Rocketbook Everyday Planner

tds_purchase_m_rocketbook_everyday_notebook
Read-onlyIdempotent

Recorded model Everyday Planner. 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_everyday_notebook"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYes
monthlyUseYes
unitsOnHandYes
offeredModelYes
unitsPerPackYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered externally. The description adds only the caution about variant naming and unit consistency, and says nothing about what is computed, what assumptions it makes, or what comes back.

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

Conciseness4/5

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

Three short, front-loaded sentences with no padding. However, the opening sentence conveys almost no information, so brevity here comes at the cost of substance rather than from efficient wording.

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 computation tool with no output schema and no documented parameters needs the description to explain the model (usage × months minus stock, divided by pack size) and the unit rule. The description covers neither the computation nor the meaning of most inputs.

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 full burden. It partially addresses offeredModel (seller's model field / exact variant name) and hints that monthlyUse, unitsOnHand and unitsPerPack share a measured unit, but months and the distinction between on-hand stock and pack size receive no explanation.

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 the fragment "Recorded model Everyday Planner," which restates the product identity rather than naming an action. It never says what the tool actually does — presumably compute a quantity or pack count from usage over time — so an agent must infer the verb from the parameter names and title.

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?

The guidance given ("Use the seller's model field or exact variant name," "Confirm the exact type, dimensions and compatibility") is about input hygiene, not about when to choose this tool over the many sibling Rocketbook/planner purchase tools. There is no when-to-use or when-not condition and no mention of alternatives.

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.