Skip to main content
Glama

The Doll Scout Home Tools

Plan materials and spare stock · Amsterdam Standard Series Acrylic Tube 120 ml

tds_purchase_m_amsterdam_amsterdam_standard_series_96bb568c
Read-onlyIdempotent

Recorded model Standard Series Acrylic Tube 120 ml. 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_amsterdam_amsterdam_standard_series_96bb568c"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectsYes
offeredModelYes
sparePercentYes
unitsPerPackYes
amountPerProjectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is fully covered. The description adds essentially nothing beyond that: it never says what is computed or recorded, whether results persist, or how the requested amount and spare percentage are combined.

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 no redundant padding, and the model-naming rule is front-loaded. But the first sentence burns space on a restatement of the product name, and the fragmented style ("checked values for the exact pack") leaves meaning ambiguous rather than compact.

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 numeric/string parameters at 0% schema coverage and no output schema, the description should explain the calculation inputs and expected result. Instead it never defines sparePercent, the unit convention across amountPerProject and unitsPerPack, or what the tool returns, leaving an agent unable to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 meaning, and it does partially: it ties offeredModel to the seller's model field or exact variant name and stresses a single consistent unit for the material. However, the three numeric parameters (projects, amountPerProject, sparePercent) and unitsPerPack receive no explanation of units, format, or what "checked values for the exact pack or accessory" actually refers to.

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 opens with "Recorded model Standard Series Acrylic Tube 120 ml," which merely restates the product in the title rather than stating what the tool does. Only the title ("Plan materials and spare stock") hints at the actual function, and nothing distinguishes this from the many near-identical per-product siblings such as the Standard Series variant ending ab7ef765.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives like tds_spare_parts_review or tds_threshold_spare_stands. The remarks about using the seller's model field and a consistent unit read as data-entry hints, not selection guidance for the agent.

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.