Skip to main content
Glama

product_warranty

Read-only

Returns warranty data only.

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": "product_warranty"
  }
}

Input Schema

NameRequiredDescriptionDefault
gtinNoGlobal Trade Item Number. Overrides brand_name + product_code. Use GTIN exclusively when valid.
localeNoLocale for this request, in the language_COUNTRY form. Applies to this request only. Omit to use the connection default. Available locales come from account_locales.
brand_nameNoBrand name. Required only with product_code. Ignored if GTIN is present.
product_codeNoManufacturer product code. Required only with brand_name. Ignored if GTIN is present.

Output Schema

NameRequiredDescriptionDefault
warrantyYesWarranty text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds essentially nothing beyond that beyond the vague scope word 'only' – no auth requirements, no rate limits, no note on how GTIN vs brand/product_code affects resolution.

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?

A single front-loaded sentence with zero filler, and the scope word 'only' is placed to do what little work it can. It is not bloated, though it is arguably undersized for a four-parameter tool.

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 an output schema present the return values need not be described, and annotations carry the safety profile. The remaining gap is routing guidance against the many product_* siblings, which is exactly what the description fails to supply.

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 the schema already explains GTIN overriding brand_name/product_code, the language_COUNTRY locale format, and the account_locales dependency. The description adds no parameter meaning, so the baseline 3 is correct.

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?

States the resource (warranty data) and a generic verb (returns), and the word 'only' faintly signals it does not return the other product data the siblings cover. However it never names a sibling or distinguishes itself concretely from product_360_view or product_specs, so an agent gets only a vague sense of scope.

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?

There is no explicit when-to-use guidance, no prerequisites, and no named alternative. The qualifier 'only' implies a boundary but requires the agent to infer it against 19 sibling tools.

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