get_mappit_infoAbout Mappit itself: what it is, its version, how many stories, storylines and places it holds right now, the topic list (the slugs other tools accept as topic), and which countries it covers. Use to learn valid topics.
| Name | Required | Description | Default |
|---|---|---|---|
| include | No | Sections, any of: pulse, topics, countries, token. Default: pulse and topics. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish that this is a safe, read-only, idempotent, closed-world operation. The description adds some useful context by saying counts are current and topics are accepted by other tools, but it does not discuss freshness guarantees, token handling, or other behavioral limits beyond that.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded and efficiently enumerates the main information returned. The final sentence slightly repeats the topic-list point, but overall it is compact and readable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description adequately explains the returned information: Mappit identity, version, counts, topics, and countries. It leaves `pulse` and `token` sections unexplained, but the schema documents those section names.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage for the single optional `include` parameter, including valid sections and defaults, so the schema does the heavy lifting. The description does not mention the `include` parameter or explain how sections like `pulse` or `token` affect the result.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states this is a metadata tool about Mappit itself, listing version, counts, topics, and countries. It distinguishes itself from search/list siblings by noting the topic list contains slugs other tools accept, though it does not explicitly name alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives a clear use case: learn valid topics for other tools. It does not state when not to use it or name alternative metadata/digest tools, so it falls short of full when/when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.