Mogean POI data store

Search the catalog

search

Read-onlyIdempotent

Search Mogean's catalog of US point-of-interest datasets: brands, categories, states, government sources and flagship datasets. Returns matching products with an id, title, URL and short text; pass an id to fetch for the full product card.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

Name	Required	Description	Default
`kinds`	No	Limit results to these product kinds.
`limit`	No	Results per page (default 10, at most 50).
`query`	Yes	What to look for, e.g. a brand, category, state or registry name.
`cursor`	No	next_cursor from a previous page of the same search.
`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.

Changed1 schema field changedOct 30, 2026

addedOutput schema / properties / data / properties / results / items / properties / also_from

Added value: +{
+  "description": "Brands only, and only on a suggestion rather than a match: the parent company this brand shares with a brand the query matched (or the parent company the query named). Absent on every direct match.",
+  "type": "string"
+}

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond them by disclosing the return payload shape and the follow-up call pattern; it omits relevance/ordering behavior and any rate or scope limits.

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 sentences, zero filler. The domain scope is front-loaded and the follow-up workflow is placed last where it reads as the next action.

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?

With an output schema and 100% parameter coverage, the description only needs to frame scope and return semantics, which it does. Pagination via cursor and the response_format trade-off are left entirely to the schema, which is a minor residual gap.

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 100%: query, kinds enum, limit bounds, cursor and response_format are all documented inline. The description adds no parameter-level detail beyond schema, so the baseline 3 applies.

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?

Names a specific verb (search) plus the concrete resource set (US point-of-interest datasets: brands, categories, states, gov sources, flagship datasets) and states what comes back (id, title, URL, short text). The final clause routes the agent to `fetch` for full detail, so it is distinguishable from its main sibling without opening either schema.

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?

The 'pass an id to fetch for the full product card' sentence establishes the search-then-fetch workflow clearly. It stops short of naming when to prefer the other siblings (mogean_count, mogean_quote, mogean_preview, mogean_catalog_info) or any exclusion cases.

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?