Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · MOFT Adhesive Laptop Stand

tds_purchase_m_moft_moft_stand_adhesive
Read-onlyIdempotent

Recorded model Adhesive Laptop 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_moft_stand_adhesive"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
otherDevicesWYes
reservedWattsYes
primaryDeviceWYes
continuousBudgetWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds that this is a pure arithmetic comparison rather than a lookup, which is useful, but it never says what the computation returns (headroom, pass/fail, warnings) even though there is no output schema to explain it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, no repetition, with the core purpose front-loaded. The closing sentence about voltage, connectors, per-port limits and the setup guide is only loosely tied to the actual watt-only parameters and is the weakest part.

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, no output schema, and no annotations describing the result: an agent does not know what it gets back or how to interpret the comparison. The description also does not explain reservedWatts or the expected magnitude of inputs, leaving a substantial gap for a computation tool.

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 full burden. It does map 'declared continuous allowance' to continuousBudgetW and 'provided device loads' to the device watt inputs, but reservedWatts is never explained and units, the primary/other split, and the meaning of distinct fields are left to inference.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific operation — an arithmetic comparison of a declared continuous power allowance against provided device loads — and ties it to the recorded 'Adhesive Laptop Stand' product. It is distinguishable from sibling product tools, though it never explicitly contrasts itself with them.

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?

The only usage instruction is 'Use the seller's model field or exact variant name' for identifying the model. There is no statement of when this comparison should be run versus other tools, no prerequisites, and no exclusions; 'Check voltage, connectors, per-port limits and the setup guide' is a caveat, not routing 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.