Mogean POI data store

Preview rows

mogean_preview

Read-onlyIdempotent

Show up to 10 sample rows from one brand's dataset, with the sources and licences they come from. The timezone column is withheld.

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": {
      "slug": "<slug>"
    },
    "name": "mogean_preview"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	A brand: the id search returned (brand:<slug>) or the bare slug from fetch's metadata.key.
`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

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower, yet the description still adds real behavioral context beyond them: the hard 10-row result cap and the deliberate withholding of the timezone column, which signals partial output the agent should not treat as a complete dataset. It stops short of mentioning error behavior for an unknown slug or any rate/permission considerations.

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?

Two short sentences with zero filler. The scope and row cap come first, and the two notable caveats (sources/licences included, timezone withheld) follow immediately.

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?

An output schema exists, so return structure need not be explained, and the description covers scope, result cap, and a deliberate field exclusion. It is close to complete; only the failure path for an unrecognized slug is unaddressed for a tool that has one required identifier parameter.

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%: the slug parameter already documents both the brand:<slug> form and the bare metadata.key form, and response_format's enum and default are fully described. The description only restates 'one brand's dataset' and adds no format or validation semantics beyond the schema, so baseline 3 applies.

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?

The description gives a specific verb (Show) and resource (up to 10 sample rows from one brand's dataset), plus what accompanies them (sources and licences) and one exclusion (timezone column withheld). It is clear what the tool does, but it never names or contrasts the sibling tools (fetch, search, mogean_count, mogean_catalog_info), so an agent must infer the distinction itself.

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 only implied: 'sample rows' and the 10-row cap suggest a preview/inspection step before committing to a full fetch, but the description never states when to call this instead of fetch or search. There are no prerequisites, exclusions, or alternative-routing guidance.

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?