Skip to main content
Glama

The Doll Scout Home Tools

Plan materials and spare stock · Amsterdam Standard Series Acrylic Jar 500 ml

tds_purchase_m_amsterdam_amsterdam_standard_series_ab7ef765
Read-onlyIdempotent

Recorded model Standard Series Acrylic Jar 500 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_ab7ef765"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectsYes
offeredModelYes
sparePercentYes
unitsPerPackYes
amountPerProjectYes

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 already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it never says the tool plans/computes material and spare quantities, whether results are persisted, or what the response contains, despite the title promising a planning computation.

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 padding, but the first simply restates the product name instead of front-loading the action, and 'checked values for the exact pack or accessory' is jargon that does not resolve into a concrete instruction. It is brief but poorly ordered relative to what an agent needs first.

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-numeric-parameter planning tool with no output schema and no parameter documentation, and the description omits the crucial relationship among projects, amountPerProject, unitsPerPack and sparePercent (how quantity and spare allowance are derived). An agent could populate plausible-looking values that mean the wrong thing, which is a real risk here.

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% with five required parameters, so the description must carry the load. It meaningfully clarifies only offeredModel ('seller's model field or exact variant name'); the unit remark is ambiguous ('one consistent unit for the material and checked values for the exact pack or accessory'), and it says nothing about projects, amountPerProject, unitsPerPack, or sparePercent.

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 itself contains no action verb: 'Recorded model Standard Series Acrylic Jar 500 ml' merely identifies the SKU, and the only purpose statement ('Plan materials and spare stock') lives in the title. Because the siblings are near-identical per-product variants (e.g., tds_purchase_m_amsterdam_amsterdam_standard_series_96bb568c), naming the product is the useful differentiator, but the action is only inferable from the title.

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 or when-not-to-use guidance and no named alternative among the many sibling purchase/stock tools. What guidance exists ('Use the seller's model field or exact variant name') is input-format advice rather than tool-selection advice, leaving the agent unable to tell this apart from sibling SKU variants except by product name.

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.