Skip to main content
Glama

The Doll Scout Home Tools

Plan paper or media use · Zebra Pen DelGuard Mechanical Pencil

tds_purchase_m_zebra_pen_delguard_mechanical_pencil
Read-onlyIdempotent

Recorded model DelGuard Mechanical Pencil. 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_delguard_mechanical_pencil"
  }
}

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 declare the tool is read-only, idempotent, and non-destructive, but the description does not explain what the tool actually does—e.g., whether it computes a purchase plan or returns a recommendation. It adds no behavioral context beyond the product name and parameter hints.

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 three short sentences, but it is not front-loaded with purpose—it opens with the product name rather than the action. The final sentence ('Confirm the exact type, dimensions and compatibility') is vague and does not earn its place.

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 planning tool with five required inputs and no output schema, the description omits the core calculation logic and what the tool returns. An agent cannot confidently predict the result of invoking it.

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?

With 0% schema description coverage and five required parameters, the description only partially clarifies offeredModel and unit consistency across monthlyUse, unitsOnHand, and unitsPerPack. It leaves months and unitsOnHand largely unexplained beyond their names.

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?

The description names the specific product (DelGuard Mechanical Pencil) but does not state the action, such as calculating required units or planning a reorder. The title hints at planning, but the description alone only identifies the resource, leaving the tool's core purpose vague.

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?

It offers parameter-entry advice (use the seller's model field, use the same measured unit) but gives no guidance on when to use this tool versus sibling tools or what prerequisites are needed. The agent must infer that this tool is for this specific product.

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.