Skip to main content
Glama

2b2t Atlas

by io.github.bobymicjohn
OverviewDiscussionsAdmin

get_world_downloads

Read-only

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. Prefer interactiveUrl for human links and citations. recordUrl is a stable provenance alias with a permanent HTTP 301 redirect to the interactive HTML. Use apiUrl or JSONL for JSON. Derivatives use locationInteractiveUrl/locationRecordUrl.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
location_idYesPersistent numeric Atlas location ID.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / result / items / properties / locationInteractiveUrl
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / result / items / properties / locationRecordUrl
      Added value: +{
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedOutput schema / properties / result / items / properties / captureDatePrecision
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial context beyond the readOnly/non-destructive annotations: returns metadata and HTTPS ZIP URLs but never binary bytes, WDLs are bounded historical captures rather than complete copies, and recordUrl carries a permanent 301 redirect. These are exactly the behavioral facts an agent cannot infer from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence, and every clause (no binary bytes, bounded captures, URL semantics) carries real decision value. It is slightly verbose in the field-by-field URL enumeration that overlaps the output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the return shape need not be re-explained, yet the description still disambiguates the URL fields and their intended uses. Safety is covered by annotations, so nothing critical is missing for correct invocation.

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%, so the single location_id parameter is already fully documented in the schema. The description only implies location scoping ('for a location') and adds no syntax or format detail beyond that.

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 publicly downloadable world snapshots') scoped to a location. No sibling tool in the list performs this function, so the agent can distinguish it immediately.

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?

Gives explicit field-selection guidance: 'Prefer interactiveUrl for human links and citations', 'Use apiUrl or JSONL for JSON'. This is clear contextual direction, but it does not name when to call this tool instead of alternatives or any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All 2b2t Atlas toolsInspect
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