Skip to main content
Glama

The Doll Scout Home Tools

Plan materials and spare stock · Faber-Castell Pitt Pastel Pencil

tds_purchase_m_faber_castell_pitt_pastel_pencil
Read-onlyIdempotent

Recorded model Pitt Pastel Pencil. 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_faber_castell_pitt_pastel_pencil"
  }
}

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only a unit-consistency convention; it does not disclose what the call produces (a computed plan? a stored record?), how sparePercent is applied, or what happens with the required projects/amountPerProject values.

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?

It is short and wastes no padding, but the opening fragment conveys almost nothing and the two conventions that follow are not front-loaded or grouped by parameter. Brevity here reflects under-specification rather than disciplined 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?

For a tool with five required numeric inputs, no output schema, and no annotations describing the computation, the description is far too thin: an agent cannot tell what sparePercent does, what the response contains, or how the pack/unit values interact with projects and amountPerProject.

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 carry the burden. It loosely maps offeredModel to "the seller's model field or exact variant name" and unitsPerPack to "the exact pack or accessory," but projects, amountPerProject, and sparePercent are never explained, leaving three of five numeric inputs with no semantics at all.

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 Pitt Pastel Pencil" restates the product name in the tool title rather than stating an action; it never says the tool records a purchase plan, computes material quantities, or reserves spare stock. An agent can infer the subject (this specific pencil) but not the operation, and nothing distinguishes it from the many sibling tds_purchase_m_* tools beyond the product identity already encoded in the 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?

The sentences "Use the seller's model field or exact variant name" and "Use one consistent unit" are input conventions, not usage guidance. There is no statement of when this tool applies versus the sibling purchase tools for other pencils/pastels, nor any prerequisite or exclusion.

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.