Skip to main content
Glama

The Doll Scout Home Tools

Plan paper or media use · Leuchtturm1917 Quarterly Daily Planner 2027

tds_purchase_m_leuchtturm1917_quarterly_daily_planner_2027
Read-onlyIdempotent

Recorded model Quarterly Daily Planner 2027. 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_leuchtturm1917_quarterly_daily_planner_2027"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYes
monthlyUseYes
unitsOnHandYes
offeredModelYes
unitsPerPackYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/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 a closed world, so safety is covered. The description adds only a vague constraint ("same measured unit for your task and the package") and an unactionable caution to "confirm type, dimensions and compatibility" without supplying any values or explaining what the call returns or how the numbers are combined.

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?

It is short and contains no filler, but the opening sentence duplicates the title and model name instead of front-loading the task. The remaining two sentences are generic cautions rather than a clear, ordered explanation of what the call does.

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 parameters, no schema descriptions, and no output schema, the definition should explain the computation and the meaning of each input; instead it leaves the agent guessing what result is produced and how the inputs interact. For a planning/calculation tool this is a substantial gap.

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 carries the full burden, yet it explains only that offeredModel should match the seller's model or exact variant name. It says nothing about what monthlyUse, months, unitsOnHand or unitsPerPack mean individually or how they relate (e.g., whether unitsPerPack converts demand into packs), leaving four of five required integers and their bounds unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Recorded model Quarterly Daily Planner 2027" identifies the specific SKU and implicitly frames this as a per-model planning entry, but it never states the actual operation (e.g., computing how many packs to buy from monthly use, months, and on-hand stock). The model name does distinguish it from the many sibling planner SKUs, so it is not a pure tautology, but the verb is missing.

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 guidance on when to choose this tool versus a sibling planner tool or versus the adjacent framing/paper-sleeve tools; a user is left to infer selection purely from the SKU in the tool name. The sentences about using the seller's model field and confirming type/dimensions are parameter-entry advice, not usage conditions.

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.