Skip to main content
Glama

The Doll Scout Home Tools

Plan materials and spare stock · Ohuhu Chrome Paint Pen

tds_purchase_m_ohuhu_ohuhu_chrome_paint_pen
Read-onlyIdempotent

Recorded model Chrome Paint Pen. Use the seller’s model field or exact variant name. Use one consistent unit for the material and checked values for the exact pack or accessory.

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>",
      "projects": "<projects>",
      "amountPerProject": "<amountPerProject>",
      "unitsPerPack": "<unitsPerPack>",
      "sparePercent": "<sparePercent>"
    },
    "name": "tds_purchase_m_ohuhu_ohuhu_chrome_paint_pen"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectsYes
offeredModelYes
sparePercentYes
unitsPerPackYes
amountPerProjectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds nothing beyond that: it does not say what the tool computes or returns, whether a prior quote/budget step is needed, or how sparePercent affects the outcome.

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 with little waste, but the opening is cryptic ("Recorded model") and the instruction ordering buries the material/unit guidance after a naming note. Brevity here comes at the cost of clarity rather than through tight editing.

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?

A five-required-parameter planning/computation tool with no output schema and no schema descriptions needs the description to explain what each quantity drives. Instead it covers only naming and unit consistency, leaving the agent unable to reason about the numeric inputs before calling.

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% for five required parameters, so the description must compensate, and it only speaks to two: offeredModel (seller model field or exact variant) and pack/accessory values tied to unitsPerPack. projects, amountPerProject, and sparePercent — the quantitative core — are left completely 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?

"Recorded model Chrome Paint Pen" restates the product name rather than stating what the tool does with it. Only the title ("Plan materials and spare stock") hints that this computes material and spare-stock quantities, and the description never uses a verb describing the operation.

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 "Use one consistent unit..." give input-entry conventions, not when to choose this tool over the sibling purchase tools listed. No exclusion, prerequisite, or alternative is named.

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.