Skip to main content
Glama

Muretai Catalog

Look up one shop

catalog.lookup
Read-only

Return the catalog record of one indexed shop, from its origin (https://shop.example) or from any page URL on it, such as a product link. The record is the same JSON as GET /catalog/shop?origin=: name, provenance, DID and Agent Card URL when signed or claimed, and when the catalog last read it. Stored data only: nothing is fetched. A host the catalog has not indexed is refused by name.

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": {
      "url": "<url>"
    },
    "name": "catalog.lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe shop's origin or a page URL on it (http or https).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that only stored data is read and nothing is fetched (reinforcing openWorldHint=false with concrete meaning), that any page URL on the origin resolves to the same shop record, and the failure mode for unindexed hosts. That is exactly the behavioral context an agent needs before calling.

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?

Four tight sentences, front-loaded with the purpose, then input flexibility, then return shape, then failure mode. The reference to the equivalent GET endpoint is informative rather than padding, and nothing is repeated from the schema verbatim.

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?

With no output schema, the description compensates by naming the returned fields (name, provenance, DID, Agent Card URL when signed or claimed, last-read time). Combined with the single well-documented parameter, an agent has everything needed to call it correctly and interpret the result.

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 earns above baseline by explaining that a product link or any page URL on the origin is an acceptable value and resolves to the shop record, which is the non-obvious part of the parameter's semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Return the catalog record of one indexed shop'. The scope (one shop, keyed by origin or any page URL on it) cleanly separates it from catalog.search (many results) and catalog.get_product (product-level records).

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 rather than stated: you call it when you have a shop URL and want its catalog record. It does give a useful edge-case rule (a host the catalog has not indexed is refused by name), but it never explicitly contrasts with catalog.get_product or catalog.search for the case where the caller has a product link and wants product data rather than the shop record.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources