Skip to main content
Glama

The Doll Scout Home Tools

Plan materials and spare stock · ARTDOT Butterfly Diamond Painting Kits

tds_purchase_m_artdot_diamond_painting_kit_butterfly
Read-onlyIdempotent

Recorded model Butterfly Diamond Painting Kits. 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_artdot_diamond_painting_kit_butterfly"
  }
}

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 unit-consistency advice and says nothing about how sparePercent influences the result, whether the computation rounds up, or what a conflicting unit produces—behavioral traits an agent cannot infer from 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?

Two short sentences with no filler, so it is not bloated. However, the leading sentence is a near-tautology, meaning the limited space is spent poorly rather than front-loading the operation and its inputs.

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-parameter, all-numeric planning tool with no output schema and no parameter descriptions requires the description to explain how the quantities combine. What is present covers only naming and unit consistency, leaving the core calculation and the role of sparePercent undocumented.

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 five required parameters, so the description must carry the full burden. It gestures at offeredModel ('seller's model field or exact variant name') and at unitsPerPack/amountPerProject ('one consistent unit'), but projects and sparePercent are never explained and the unit-consistency relationship between the two numeric fields is left implicit.

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 Butterfly Diamond Painting Kits,' which essentially restates the tool name and title rather than stating a verb or operation. Only the title ('Plan materials and spare stock') hints at the actual function, and the description never says it computes pack counts from projects, amountPerProject, unitsPerPack and sparePercent.

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 only guidance is 'Use the seller's model field or exact variant name,' which is input-format advice rather than when-to-use guidance. No condition distinguishes this from siblings such as tds_spare_parts_review or tds_threshold_spare_stands, and no exclusions or prerequisites are stated.

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.