Skip to main content
Glama

The Doll Scout Home Tools

Plan paper or media use · Zebra Pen Zensations Brush Pen

tds_purchase_m_zebra_pen_zensations_brush_pen
Read-onlyIdempotent

Recorded model Zensations Brush Pen. 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_zebra_pen_zensations_brush_pen"
  }
}

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds a real constraint—"Use the same measured unit for your task and the package"—plus a caution to confirm type, dimensions and compatibility, but never explains what is computed or returned, which is the main remaining behavioral gap.

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, so there is no bloat, but the lead sentence is spent restating the model name instead of front-loading the purpose. The remaining sentences are terse instructions rather than a structured explanation of the operation.

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?

This is a five-required-parameter planning calculation with no output schema and no annotations describing results, so the description carries the full burden of explaining the computation. It omits how monthlyUse, months, unitsOnHand and unitsPerPack combine into a plan, leaving the agent unable to predict what it will get back.

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 all five required parameters, yet it only hints at offeredModel (seller's model field / exact variant name) and obliquely at units via the "same measured unit" sentence. monthlyUse, months, unitsOnHand and unitsPerPack get no meaning at all—no definition of the unit, no note that months caps at 120, no relationship between use rate and pack size.

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 opening "Recorded model Zensations Brush Pen" mostly restates the tool name and product title rather than saying what the tool does. The actual action (planning usage/purchase quantity for this specific product) is only inferable from the title "Plan paper or media use", not from the description itself, so an agent cannot tell from the text alone what computation it performs.

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?

"Use the seller's model field or exact variant name" tells the agent how to fill a parameter, not when to choose this tool over the many sibling product-planning tools. There is no statement of when to use it, when not to, or what distinguishes it from e.g. the Mildliner or Metallic Brush Pen variants.

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.