Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · MOFT Modular pen holder

tds_purchase_m_moft_modular_pen_holder
Read-onlyIdempotent

Recorded model Modular pen holder. Use the seller’s model field or exact variant name. This arithmetic compares a declared continuous allowance with provided device loads. Check voltage, connectors, per-port limits and the setup guide.

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>",
      "continuousBudgetW": "<continuousBudgetW>",
      "primaryDeviceW": "<primaryDeviceW>",
      "otherDevicesW": "<otherDevicesW>",
      "reservedWatts": "<reservedWatts>"
    },
    "name": "tds_purchase_m_moft_modular_pen_holder"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
otherDevicesWYes
reservedWattsYes
primaryDeviceWYes
continuousBudgetWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the tool is pure arithmetic over supplied numbers, which is consistent and mildly reinforcing. It adds no context on what the result means (pass/fail, margin, warnings), and the 'check voltage, connectors, per-port limits' sentence hints at constraints the tool apparently does not enforce.

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 sentences, no filler words, but poorly front-loaded: the product-record and model-name instructions come before the actual function, and the final checklist sentence is a dangling caution. The result reads as two different tool descriptions spliced together.

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-required arithmetic tool with no output schema needs the description to state the computation and what the returned comparison looks like. Neither is provided, and one parameter (reservedWatts) and the unit handling are entirely undocumented. An agent can supply numbers but cannot predict or interpret the result.

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 load. It gestures at continuousBudgetW ('declared continuous allowance') and at primaryDeviceW/otherDevicesW ('provided device loads'), but never explains reservedWatts, never states units or how the budget is combined with the loads, and gives no arithmetic rule. Only partial compensation for a total coverage gap.

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 does state the operation — 'This arithmetic compares a declared continuous allowance with provided device loads' — which is more than a restatement of the name. But it opens with 'Recorded model Modular pen holder' and 'Use the seller's model field', framing it as a product-record tool, which muddies what the tool actually does. Nothing distinguishes it from the many sibling tds_purchase_* tools beyond the word 'arithmetic'.

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?

'Use the seller's model field or exact variant name' gives limited guidance on how to fill offeredModel, which is useful but parameter-level. There is no statement of when this comparison should be run, when it should not, or what alternative to use instead. The trailing 'Check voltage, connectors, per-port limits and the setup guide' is an unactionable caution rather than usage guidance.

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.