Mogean POI data store

Purchased data

mogean_my_data

Read-onlyIdempotent

List the datasets the signed-in Mogean account has bought, or one by order_id: file names and sizes, row counts, licence, data release, delivery state, and the store account page where the account holder signs in to download. Download links are never returned to the agent.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mogean_my_data"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Datasets per page of the list (default 10).
`cursor`	No	next_cursor from the previous page of the list.
`order_id`	No	An order id from this list.
`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.

AddedNov 5, 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, closed-world, non-destructive behavior, so the bar is lower. The description still adds real context the annotations cannot: a download is not possible through the agent, no download links are returned, and the account holder must sign in on the store account page — a crucial operational constraint. It does not discuss rate limits or pagination behavior, keeping it from a 5.

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, the first front-loading the core action and the second carrying the security-critical caveat. Field enumeration is dense but purposeful, and nothing is redundant padding.

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?

Output schema exists, yet the description usefully previews the returned fields (file names, sizes, row counts, licence, data release, delivery state, account page), and pagination is covered by the schema. Nearly complete for a read-only listing tool; only the concise-vs-detailed response choice is left entirely to the schema.

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 limit, cursor, order_id, and response_format are already documented, making 3 the baseline. The description adds only the framing that order_id switches from list mode to single-record retrieval; it says nothing about limit bounds, cursor chaining, or the concise/detailed tradeoff beyond the schema.

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 ('List the datasets the signed-in Mogean account has bought') plus the two operating modes (full list or a single order_id). This is clearly distinguishable from siblings like mogean_catalog_info, mogean_preview, or mogean_quote without opening any 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 'or one by order_id' clause tells the agent both modes exist and implies when to narrow the query, which is clear context for selection. It stops short of naming an alternative sibling or stating exclusions, so it is not a full when/when-not rubric.

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?