Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · MOFT Metal Lanyard Mount

tds_purchase_m_moft_metal_lanyard_mount
Read-onlyIdempotent

Recorded model Metal Lanyard Mount. 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_metal_lanyard_mount"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
otherDevicesWYes
reservedWattsYes
primaryDeviceWYes
continuousBudgetWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/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 fully covered; the description adds little beyond calling the operation 'arithmetic'. It never states what is returned (a verdict, remaining headroom, a comparison), how reservedWatts participates, or what happens when loads exceed the declared budget. The voltage/connector/per-port caveats reference no parameters in the schema, adding ambiguity rather than disclosure.

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?

Four short sentences with no wasted clauses, but the ordering is poor: the product-name framing is front-loaded while the actual operation (the arithmetic comparison) appears only in the third sentence. The final sentence about voltage, connectors, per-port limits and the setup guide does not correspond to any schema field and reads as filler.

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 five-required-parameter computation with no output schema, so the description should explain the result and the role of each input. It omits reservedWatts's purpose, the result shape, and any tolerance or failure behavior, leaving an agent unable to predict what the call produces even though it can probably construct valid arguments.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the documentation burden and does partially meet it: 'declared continuous allowance' maps to continuousBudgetW, 'provided device loads' to primaryDeviceW/otherDevicesW, and the seller-model sentence to offeredModel. However, reservedWatts is never mentioned and the 0-30000 numeric bounds and watt units are left entirely implicit.

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 title and the sentence 'This arithmetic compares a declared continuous allowance with provided device loads' identify a power-budget comparison, but the opening 'Recorded model Metal Lanyard Mount' frames it as a product-record lookup, so the agent must reconcile two different framings. The verb is never stated outright (compute? compare? report headroom?), and nothing distinguishes it from the many sibling purchase/record tools.

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 input-sourcing guidance for one parameter, which is useful, but there is no statement of when this tool should be chosen over a sibling or when it should not be used. 'Check voltage, connectors, per-port limits and the setup guide' reads as a caveat but names no corresponding input, so it cannot guide invocation.

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.