Mogean POI data store

Fetch a product

fetch

Read-onlyIdempotent

Fetch one catalog product by the id that search returned: what it contains, coverage, fill rates, freshness, provenance and published prices per licence tier.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	A product id from search, such as brand:<slug>, or a product sku.
`response_format`	No	concise (default) returns a short summary; detailed adds the full structured result as text.	concise

Output Schema

Name	Required	Description	Default
`data`	No
`tool`	Yes
`limit`	No
`errors`	No
`status`	Yes
`message`	Yes
`drop_date`	No
`permalink`	No
`attribution`	No
`response_format`	Yes
`manifest_version`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful behavioral context by listing what the response contains — coverage, fill rates, freshness, provenance, and prices per licence tier — which tells an agent more about the payload than the annotations alone.

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?

A single front-loaded sentence states the action, the selector, and the payload, with no wasted clauses. The key retrieval instruction comes first.

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

Completeness4/5

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

The definition is complete for a read-only retrieval tool: annotations cover safety semantics, the schema fully documents both parameters, and an output schema exists for return values. Minor omissions like not-found or error behavior are acceptable given the structured coverage.

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 description coverage is 100%, so the schema already documents both the `id` format and `response_format` enum. The description reinforces the provenance of `id` ('that search returned') but does not add syntax or guidance beyond what the schema already provides, making the baseline 3 appropriate.

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?

The description uses a specific verb and resource ('Fetch one catalog product') and makes the retrieval route explicit ('by the id that search returned'), which clearly separates it from the sibling `search` tool. It also previews the product attributes returned, so an agent knows exactly what this call yields.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly establishes the prerequisite flow: the `id` comes from `search`, implying this is the follow-up detail call rather than a discovery call. It does not explicitly name when not to use this tool or contrast against `mogean_preview` or `mogean_catalog_info`, so it falls short of full alternative routing.

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

All Mogean POI data store 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?