Skip to main content
Glama

The Doll Scout Home Tools

Plan paper or media use · Leuchtturm1917 Planner Stickers 2027

tds_purchase_m_leuchtturm1917_planner_stickers_2027
Read-onlyIdempotent

Recorded model Planner Stickers 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_planner_stickers_2027"
  }
}

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 establish that this is a read-only, idempotent, non-destructive, closed-world operation, so the description need not re-state safety. It does add one real behavioral constraint — the task and the package must use the same measured unit, otherwise the result is wrong — plus a caution to verify product compatibility. However, it never says what the tool produces (e.g., recommended pack count) or that it is a pure calculation with no side effects beyond what annotations already imply.

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?

Three short sentences keep it compact, but the lead sentence is a near-worthless restatement of the product name and the useful content (model field, unit consistency, compatibility check) trails behind it. Front-loading the actual function would improve it without adding length.

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 at 0% schema coverage and no output schema, the description must explain both the inputs and the expected result. It fails to describe the purchase-quantity computation or the roles of `months`, `monthlyUse`, `unitsOnHand`, and `unitsPerPack`, leaving a caller unable to invoke the tool confidently.

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 for five required parameters. It clarifies only `offeredModel` (seller's model field or exact variant name) and vaguely gestures at unit consistency for `monthlyUse`/`unitsOnHand`/`unitsPerPack`; `months` and the distinct roles of stock-on-hand versus per-pack quantity are never explained, leaving an agent to guess at the core calculation.

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 Planner Stickers 2027," essentially restates the tool name and never states a verb or outcome such as "computes how many packs of stickers to purchase." Only the title phrase "Plan paper or media use" hints at the purpose, and nothing distinguishes this from the many sibling `tds_purchase_m_leuchtturm1917_*` planner 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?

The sentences "Use the seller's model field or exact variant name" and "Confirm the exact type, dimensions and compatibility" are data-entry instructions rather than guidance on when to choose this tool over the sibling planner/sticker tools. There is no statement of when-not to use it or what alternative applies.

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.