Skip to main content
Glama

The Doll Scout Home Tools

Plan materials and spare stock · ARTDOT Rose Diamond Painting Kits

tds_purchase_m_artdot_diamond_painting_kit_rose
Read-onlyIdempotent

Recorded model Rose 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_rose"
  }
}

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 readOnly, idempotent, non-destructive, and closed-world behavior, so the description need not repeat safety. Beyond that, it adds only input consistency advice and says nothing about what the tool computes, records, or returns.

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?

The description is brief, but the first sentence is a fragment that does not front-load the action, and the input guidance is cryptic ('checked values for the exact pack or accessory'). It avoids bloat but at the cost of clarity.

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 five-parameter planning tool with no output schema and no parameter descriptions, the definition is materially incomplete: it does not explain the planning calculation, parameter meanings, or expected result. The annotations cover safety, but not the functional context an agent needs to invoke it correctly.

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?

With 0% schema description coverage and five required parameters, the description should explain each parameter. It only loosely maps offeredModel to 'seller’s model field or exact variant name' and hints at units and checked values, leaving projects, amountPerProject, unitsPerPack, and sparePercent unexplained.

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 Rose Diamond Painting Kits,' which restates the product model rather than stating a clear action like planning materials or calculating spare stock. The title supplies the verb 'Plan,' but the description itself does not distinguish this tool from sibling purchase tools beyond the product variant.

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 gives input advice ('Use the seller’s model field or exact variant name') but no when-to-use guidance, prerequisites, or alternatives among the many sibling purchase and stock tools. The agent must infer that this is only for the Rose kit from the name and title.

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.