Skip to main content
Glama

The Doll Scout Home Tools

Plan paper or media use · STABILO BOSS ORIGINAL Highlighter

tds_purchase_d19
Read-onlyIdempotent

Recorded model 70/33. 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_d19"
  }
}

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?

The annotations already establish that this is read-only, idempotent, non-destructive, and closed-world, so safety behavior is covered. The description adds product-specific cautions about exact model, measurement units, and compatibility, but it does not explain the planning calculation or what the result represents.

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 short and front-loads the recorded model, but 'Recorded model 70/33' is cryptic without context, and the following imperative sentences do not build toward a clear tool purpose. It avoids verbosity but is under-specified rather than efficiently informative.

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-parameter planning tool with no output schema, yet the description does not explain the calculation, return value, or how the numeric inputs combine. The annotations cover safety, but the description leaves too much about the tool's actual behavior to inference.

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 the burden for five required parameters. It only indirectly addresses offeredModel via 'seller’s model field or exact variant name' and mentions consistent units, leaving monthlyUse, months, unitsOnHand, and unitsPerPack unexplained.

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 never states the action the tool performs; 'Recorded model 70/33' is catalog identity rather than a verb and resource. It gives variant and measurement cautions, but an agent cannot confidently tell whether this calculates purchase quantities, checks compatibility, or records a product.

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 advises using the seller's model field or exact variant name and matching measured units, which is useful input guidance. However, it does not say when this planning tool should be used instead of sibling purchase or quoting tools, nor does it describe prerequisites or exclusions.

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.