Flowering UCP

lookup_catalog

Slå produkter eller varianter op (UCP catalog.lookup). catalog: {ids:[...]}.

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	UCP request metadata, fx {"ucp-agent":{"profile":"https://..."}}.
`catalog`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Look up' implies a non-destructive read, but there is no disclosure of permissions, error behavior when IDs are unknown, result limits, or what the response contains.

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, front-loaded clauses with no filler. The trailing fragment is terse to the point of being cryptic, but nothing is wasted.

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?

For a tool with an undocumented nested parameter object, no annotations, and no output schema, the description is too thin: it omits return values and the relationship to sibling catalog tools. Also, the description is in Danish while the surrounding tool ecosystem is English-named, which is a minor consistency risk.

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 coverage is only 50%: 'meta' is documented in the schema while 'catalog' is a bare object with no properties. The description usefully supplies the missing shape ('catalog: {ids:[...]}'), which is real added value, but it never says what kind of IDs are accepted or what the optional meta carries.

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 ('Slå produkter eller varianter op' = look up products or variants) which is unambiguous. It does not differentiate itself from the sibling search_catalog, so an agent must infer that this is an ID-based fetch rather than a query search.

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 when-to-use, when-not-to-use, or alternative guidance. The hinted shape 'catalog: {ids:[...]}' weakly implies lookup-by-identifier versus searching, but the agent is left to infer the routing between this and search_catalog/get_product.

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

All Flowering UCP 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?