Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

adidas_product

Fetch full product-detail data for one Adidas SKU, including name, brand, category, pricing, images, and purchasable size variants.

Instructions

Get an Adidas product. Returns product-detail data for one Adidas SKU: name, brand, category, description, pricing (current/standard/sale), images, and every purchasable size variant. product_id is the Adidas SKU (e.g. JI0397), taken from a search result's products[].id field or the trailing segment of an Adidas product page URL. An unknown product_id returns a not-found error.

Input Schema

NameRequiredDescriptionDefault
product_idYesAdidas SKU/product id, from a search result's products[].id field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses the return content and the failure mode ('An unknown product_id returns a not-found error'), which is genuinely useful. It omits auth/permission requirements and any rate-limit or read-only context, leaving gaps for a no-annotation tool.

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

Conciseness5/5

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

Three sentences, front-loaded with the core action, followed by return-shape and parameter-sourcing details. No filler; each sentence earns its place.

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

Completeness5/5

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

No output schema exists, yet the description still enumerates the returned fields, parameter sourcing, and error behavior. For a single-parameter lookup tool with no annotations, nothing essential to invoking it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by giving a concrete format example (JI0397) and an extra sourcing path not in the schema ('the trailing segment of an Adidas product page URL'), so it earns above baseline.

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+resource ('Get an Adidas product') and enumerates the returned fields, so the agent knows exactly what it retrieves. It distinguishes itself from retrieval-by-search siblings only implicitly (by referencing 'a search result's products[].id'), without naming adidas_search as the source. Clear, but not fully disambiguated from siblings.

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 implied: fetch details for a known SKU. The description helpfully explains where product_id comes from (a search result's products[].id or the trailing segment of a product URL), which is argument-sourcing guidance. However, it never explicitly states when to use this vs adidas_search or other siblings, nor any exclusions.

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

Deploy Server

Other Tools