Skip to main content
Glama
Sign In

Icecat

by biz.icecat
OverviewDiscussionsAdmin

product_specs

Read-only

Returns structured technical specifications. Use only for: detailed features or attributes.

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_specs"
  }
}

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
groupsYesList of specification groups, each containing related product specifications

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that — no note on how the item is identified, no coverage of the openWorld/live-data implication, and no behavioral context at all.

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?

Two short sentences with the purpose front-loaded and no filler. The second sentence is slightly clipped and its "Use only for" scoping would read better as a full clause, but nothing is wasted.

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

Completeness4/5

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

With an output schema covering return values, full annotations, and complete schema descriptions for all four identifier/locale params, the description need not say more. The only residual gap is that it never mentions an identifier is effectively required despite zero required params, but that is documented in the schema.

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% and the schema already explains the GTIN-overrides-brand+code logic, mutual requirements, and locale behavior in detail. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("Returns structured technical specifications") and scopes it to "detailed features or attributes," which helps separate it from siblings like product_overview and product_description. It stops short of explicitly naming those siblings as alternatives, so differentiation is implied rather than stated.

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?

"Use only for: detailed features or attributes" gives a positive when-to-use condition, but names no alternative tool and no exclusion cases, even though the sibling list contains several overlapping product-content tools. Usage is implied but not routed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Icecat toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources