Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · MOFT Invisible Stand

tds_purchase_m_moft_invisible_stand
Read-onlyIdempotent

Recorded model Invisible Stand. 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_invisible_stand"
  }
}

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?

Annotations already establish readOnly=true, idempotent=true, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful framing — this is pure arithmetic over supplied values, not a live product lookup — plus cautionary notes about voltage, connectors and per-port limits. It does not disclose the comparison rule (margin, pass/fail, deficit in watts) or what the caller receives back.

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 short sentences with no severe bloat, but the structure is poor: the operative clause about arithmetic arrives second, behind an opaque 'Recorded model Invisible Stand' opener, and the trailing checklist of things to verify reads as boilerplate rather than front-loaded guidance.

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?

With five required parameters, no output schema and zero schema coverage, the description carries the full explanatory burden and does not meet it. It never states the comparison formula, whether reservedWatts is headroom or a load, or what result the agent should report — the essentials for a calculation tool.

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%, so the description must document all five required parameters and largely fails. It loosely maps continuousBudgetW to 'declared continuous allowance' and the two device parameters to 'provided device loads', and explains offeredModel, but reservedWatts is never mentioned and no parameter's units, role, or interaction (e.g., whether reserved is subtracted before comparing) is clarified.

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 sentence 'This arithmetic compares a declared continuous allowance with provided device loads' does state a verb and resource, so the computational nature is discernible. But the leading fragment 'Recorded model Invisible Stand' is cryptic and the tool is never framed relative to any alternative (e.g., a plain product lookup). An agent can guess it is a power-budget calculator, not a catalog lookup, but only after parsing past the opener.

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' is a parameter formatting instruction, not a when-to-use rule. 'Check voltage, connectors, per-port limits and the setup guide' tells the agent what else to verify but never says when this tool is the right choice or what to do instead. No exclusions or alternatives are offered.

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.