Skip to main content
Glama

The Doll Scout Home Tools

Plan materials and spare stock · Amsterdam Acrylics Create Set with 20 pieces

tds_purchase_m_amsterdam_amsterdam_acrylics_create_6baec75d
Read-onlyIdempotent

Recorded model Acrylics Create Set with 20 pieces. 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_acrylics_create_6baec75d"
  }
}

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 cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the agent knows it is a safe, repeatable read. The description adds nothing beyond that: it does not say whether a plan is computed and stored, what sparePercent does, or what the caller receives. The phrase 'Recorded model' is ambiguous enough to leave the read-vs-write nature uncertain, though it does not clearly contradict the annotations.

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 brevity comes at the cost of clarity rather than from efficiency. The leading sentence is front-loaded with product identity instead of the tool's function, so the reader gets the least useful information 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 multi-input calculation tool with five undocumented required parameters and no output schema, so the description carries the full explanatory burden and does not meet it. It never explains the computation, the units contract, or the meaning of the spare-stock inputs, leaving an agent to guess at correct invocation.

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% across 5 required parameters, so the description must compensate and largely fails. It only gestures at offeredModel (seller's model field / exact variant name) and at unit consistency for unitsPerPack/amountPerProject, leaving 'projects' and 'sparePercent' — the core planning inputs — completely unexplained, including how sparePercent interacts with the other quantities.

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 only restates the product identity ('Recorded model Acrylics Create Set with 20 pieces') and never states what the tool actually does — no verb+resource pairing describing a stock/material planning computation. An agent cannot tell from this text how it differs from the many sibling purchase/stock tools beyond the embedded product name.

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 field-level advice ('Use the seller's model field or exact variant name', 'one consistent unit') but gives no when-to-use guidance, no prerequisites, and no routing to alternatives such as the spare-parts or stock-review siblings. The one contextual line is about data entry, not tool selection.

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.