List publicly downloadable world snapshots for a location. Returns metadata and HTTPS ZIP URLs, never binary file bytes. WDLs are bounded historical captures, not complete copies of 2b2t.
| Name | Required | Description | Default |
|---|---|---|---|
| location_id | Yes | Persistent numeric Atlas location ID. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / result / items / properties / captureDatePrecisionAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already indicate this is a safe read-only operation, and the description adds valuable behavioral context beyond that: it returns metadata and ZIP URLs, never binary bytes, and the snapshots are bounded historical captures rather than complete 2b2t copies. This meaningfully clarifies expected behavior.
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 compact, front-loaded with the core action, and every sentence earns its place. It efficiently conveys scope, return behavior, and historical limitations without unnecessary elaboration.
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?
For a simple single-parameter tool with an output schema and safe annotations, the description is complete. It states what the tool lists, what it returns, what it does not return, and the nature of the data, leaving no significant ambiguity for an agent deciding to invoke it.
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 already documents location_id as a persistent numeric Atlas location ID with 100% coverage. The description adds only the contextual link that the tool operates on a location, but does not need to add more because the schema fully explains the single parameter.
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 the specific operation: listing publicly downloadable world snapshots for a location. It further distinguishes the tool by noting it returns metadata and HTTPS ZIP URLs rather than binary bytes, which differentiates it from generic data-fetching or download tools among the siblings.
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?
The description provides clear context on when to use the tool: when the agent needs publicly downloadable world snapshots for a specific location. It also implicitly warns against expecting binary file data or complete live world copies, although it does not explicitly name alternative sibling tools.
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.