Skip to main content
Glama

Check a disputed spec claim

check_spec_claim
Read-onlyIdempotent

Looks up recorded spec disputes: where a brand figure and other sources disagree (for example total watts or capacity), with every figure, its condition and its own source URL, and which figure SpecSource adopted (settled) or that it is still open. Search by product or by words in the question.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_spec_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of text fields (notes, labels, answers). One of: "en" (English), "zh-hant" (Traditional Chinese), "zh-hans" (Simplified Chinese). Default "en". Spec values and model numbers are the same in every language. Example: "zh-hant".en
queryNoOptional. Space-separated words (2 to 120 characters) that must all appear in the claim's question, answer, reason or figures, in any of the three languages. Example: "210W" or "TBW".
productNoOptional. The product whose claims to look up: slug, model number or words from its name (1 to 120 characters, case ignored). At least one of product, query or category is required. Example: "PB200U" or "CUKTECH 15 Ultra".
categoryNoOptional. Only claims in this category. One of: "chargers", "power-banks", "usb-c-cables", "mini-pcs", "kvm-switches", "usb-c-docks", "ssds", "nas", "wireless-chargers", "monitors", "memory", "power-supplies", "cpu-coolers", "graphics-cards", "video-cables", "ethernet-cables", "pc-power-cables", "usb-cables". Can be used alone to list a category's claims (up to 10). Example: "ssds".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Optional. Only claims in this category. One of: \"chargers\", \"power-banks\", \"usb-c-cables\", \"mini-pcs\", \"kvm-switches\", \"usb-c-docks\", \"ssds\", \"nas\", \"wireless-chargers\", \"monitors\", \"memory\", \"power-supplies\", \"cpu-coolers\", \"graphics-cards\", \"video-cables\", \"ethernet-cables\", \"pc-power-cables\", \"usb-cables\". Can be used alone to list a category's claims (up to 10). Example: \"ssds\"."
    • changedInput schema / properties / lang / description
      Previous value: -"Language for text fields: en, zh-hant (Traditional Chinese) or zh-hans (Simplified Chinese)."New value: +"Language of text fields (notes, labels, answers). One of: \"en\" (English), \"zh-hant\" (Traditional Chinese), \"zh-hans\" (Simplified Chinese). Default \"en\". Spec values and model numbers are the same in every language. Example: \"zh-hant\"."
    • changedInput schema / properties / product / description
      Previous value: -"Slug, model number or name of the product."New value: +"Optional. The product whose claims to look up: slug, model number or words from its name (1 to 120 characters, case ignored). At least one of product, query or category is required. Example: \"PB200U\" or \"CUKTECH 15 Ultra\"."
    • changedInput schema / properties / query / description
      Previous value: -"Words to find in the claim, for example \"210W\" or \"TBW\"."New value: +"Optional. Space-separated words (2 to 120 characters) that must all appear in the claim's question, answer, reason or figures, in any of the three languages. Example: \"210W\" or \"TBW\"."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety bar is low. The description adds genuine value beyond them by disclosing the shape of the response – every claimed figure with its test condition and its own source URL, plus the adopted 'settled' figure or an 'open' status – which matters because there is no output schema.

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?

One dense but well-ordered sentence: purpose first, then response content, then how to search. Every clause carries information and nothing is padded, though the final search clause is close to redundant with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does the essential work of explaining what comes back. It still leaves gaps an agent would want: how many results to expect, whether a category-only search is limited to 10 (only stated in the schema), and how results are ordered when a product has many disputes.

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 100%, so all four parameters, including the language enum and category enum, are already fully documented in the schema. The closing sentence ('Search by product or by words in the question') only loosely restates the product and query parameters and is actually less precise than the schema, which says query matches question, answer, reason or figures.

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 uses a specific verb and resource ('Looks up recorded spec disputes') and explains the payload – conflicting figures, each with its condition and source URL, plus which figure was adopted or that the dispute is still open. It is clear enough to distinguish this from generic product lookup siblings, though it never names an alternative to contrast against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the title and first clause signal you come here when a spec value is disputed or contested. There is no explicit when-to-use versus siblings like get_product or compare_products, and no statement of when this tool is not appropriate.

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.

Resources