Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · MOFT Airflow Stand

tds_purchase_m_moft_airflow_stand
Read-onlyIdempotent

Recorded model Airflow 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_airflow_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?

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the tool is purely arithmetic and hints that voltage, connectors, per-port limits and the setup guide are outside the calculation, which is genuinely useful scoping. It still does not say what the computed result represents or whether any validation or failure mode exists.

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 short and front-loads the model identification, but the sentencs are loosely ordered and the phrase "Recorded model Airflow Stand" reads as boilerplate. Most of the content earns its place, though the middle sentence about arithmetic should come first.

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?

Five required numeric parameters with zero schema documentation and no output schema leave significant gaps. The description never states what the tool returns (headroom, pass/fail, per-port breakdown) nor how the wattage inputs combine, which an agent needs to call it correctly and 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% for five required parameters, so the description must carry the burden. It maps only obliquely: "declared continuous allowance" plausibly corresponds to continuousBudgetW, and "provided device loads" to primaryDeviceW and otherDevicesW, but reservedWatts is never explained, offeredModel's expected format is only loosely described, and no units or interaction between the wattage fields is given.

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 identify the operation as an arithmetic comparison between a declared continuous allowance and provided device loads, and names the specific product model. But it never uses a clean verb+resource framing, and the opening line "Recorded model Airflow Stand" is ambiguous, so an agent must infer that this is a power-budget check rather than an actual purchase despite the tds_purchase_ prefix.

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 input guidance, not when-to-use guidance. There is no statement of when this tool applies versus when it does not, no prerequisites, and no routing to any alternative for a different product or a different kind of calculation.

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.