Freedom Rave Wear

Look up products and variants

lookup_catalog

Read-onlyIdempotent

Look up up to 10 FRW product or variant IDs returned by this catalog. Unknown IDs return not_found messages.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "catalog": "<catalog>"
    },
    "name": "lookup_catalog"
  }
}

Input Schema

Name	Required	Description	Default
`meta`	No
`catalog`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world. The description adds genuine behavioral information beyond them: the 10-ID batch ceiling and that unknown IDs yield not_found messages rather than failing the call. It says nothing about what a successful hit returns or whether partial results are allowed.

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, front-loaded with the core action and batch limit. There is a small typo ('Look up up to 10') and no wasted clauses.

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

Completeness2/5

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

With nested objects, zero schema description coverage and no output schema, an agent needs to know what the profile URI is for and why address_country affects catalog results. Neither is mentioned, so the description is materially incomplete for this schema.

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

Parameters2/5

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

Schema description coverage is 0% and the schema is nested, so the description must carry the load. It only restates the ids array and its maximum (already in maxItems) and leaves the meta.ucp-agent.profile URI field and catalog.context.address_country entirely unexplained.

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 (look up) and resource (FRW product or variant IDs) and scopes it to identifiers previously returned by the catalog. That distinguishes it reasonably from search_catalog, though the relation to get_product (which presumably fetches one item) is not addressed.

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?

The phrase 'IDs returned by this catalog' implies this is a follow-up to a search/list call rather than a discovery tool, which is useful implied routing. But no sibling is named and no explicit when-not-to-use condition is given.

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

All Freedom Rave Wear tools Inspect

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

Need Help?