Retrieve Gymshark storefront metadata from a fixed server-side URL. Returns clean JSON for commerce data without requiring a URL parameter.
Get Gymshark store metadata. Returns storefront metadata for Gymshark (https://row.gymshark.com). The storefront URL is fixed server-side, so no url parameter is accepted.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.16.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It helpfully discloses that the storefront URL is fixed server-side so no parameter is needed, which is a genuine behavioral fact. It does not mention authentication, rate limits, or what fields the returned metadata contains.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences, front-loaded with the purpose and followed by the constraint that prevents misuse. No filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter read tool this is nearly adequate, but with no output schema the description should say more about what 'storefront metadata' actually contains (currency, markets, locale, etc.) so an agent knows whether it satisfies the need.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the baseline is 4. The description goes slightly further by explaining why no parameter exists (URL fixed server-side), which clarifies the empty schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: retrieves Gymshark storefront metadata. This cleanly distinguishes it from sibling tools like gymshark_products, gymshark_collections, and gymshark_page, though it does not explicitly name those distinctions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied by the resource description (fetch storefront metadata), and the note that no `url` parameter is accepted usefully steers invocation. However, it never states when an agent should call this instead of the other Gymshark catalog endpoints.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.