2b2t Atlas

get_nocom_dataset

Read-only

Discover NoCom World Pulse and Find data with complete-source manifests, checksums, native dimensions and human map links. Use get_nocom_daily_dataset and get_nocom_daily_hits for exact UTC days and daily maps; get_nocom_periods remains fixed 30-day buckets starting March 2020. Daily raw-source coverage includes legacy dates. Use research_nocom_area for a bounded synthesis, find_nocom_storage, search_nocom_signs, find_nocom_portals, find_nocom_clusters or find_nocom_rare_blocks for details. Source links expose full sign histories, portal blocks and cluster footprints. Observations are historical, not players, current inventories or ownership.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`find`	No
`name`	Yes
`caveats`	Yes
`sourceUrl`	Yes
`dimensions`	Yes
`attribution`	Yes
`groupedRows`	Yes
`manifestUrl`	Yes
`canonicalUrl`	No
`observations`	Yes
`periodsApiUrl`	Yes
`clustersApiUrl`	No
`sourceProducts`	No
`dailyHitsApiUrl`	No
`periodLayerCount`	Yes
`rareBlocksApiUrl`	No
`signHistoryApiUrl`	No
`exploitPatchedDate`	Yes
`groupedServerScope`	Yes
`highwaySourceScope`	Yes
`rawSourceSchemaUrl`	No
`groupedSourceSha256`	Yes
`highwaySourceSha256`	Yes
`rawSourceReleaseUrl`	No
`specialBlocksApiUrl`	No
`tilesGeneratedAtUtc`	Yes
`highwayActivityApiUrl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 5, 2026

addedOutput schema / properties / clustersApiUrl

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / dailyHitsApiUrl

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / rareBlocksApiUrl

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / rawSourceReleaseUrl

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / rawSourceSchemaUrl

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / signHistoryApiUrl

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / sourceProducts

Added value: +{
+  "items": {
+    "properties": {
+      "atlasAccess": {
+        "type": "string"
+      },
+      "contains": {
+        "type": "string"
+      },
+      "file": {
+        "type": "string"
+      },
+      "interpretation": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "file",
+      "contains",
+      "atlasAccess",
+      "interpretation"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

addedOutput schema / properties / specialBlocksApiUrl

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed3 schema fields changedSep 22, 2026
- addedOutput schema / properties / find / properties / portalsApiUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / find / properties / signsApiUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / find / properties / storageApiUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

Changed1 schema field changedSep 22, 2026

addedOutput schema / properties / find

Added value: +{
+  "properties": {
+    "accessNotes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "attribution": {
+      "type": "string"
+    },
+    "blockObservationFromUtc": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "blockObservationToUtc": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "canonicalUrl": {
+      "type": "string"
+    },
+    "complete": {
+      "type": "boolean"
+    },
+    "counts": {
+      "properties": {
+        "clusterRoots": {
+          "type": "integer"
+        },
+        "portalBlocks": {
+          "type": "integer"
+        },
+        "portalGroups": {
+          "type": "integer"
+        },
+        "signObservations": {
+          "type": "integer"
+        },
+        "signPositions": {
+          "type": "integer"
+        },
+        "storagePositions": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "storagePositions",
+        "signPositions",
+        "signObservations",
+        "clusterRoots",
+        "portalGroups",
+        "portalBlocks"
+      ],
+      "type": "object"
+    },
+    "coverage": {
+      "items": {
+        "properties": {
+          "dimension": {
+            "type": "string"
+          },
+          "products": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "sourceDimension": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "dimension",
+          "sourceDimension",
+          "products"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "id": {
+      "type": "string"
+    },
+    "integritySha256": {
+      "type": "string"
+    },
+    "integrityUrl": {
+      "type": "string"
+    },
+    "manifestSha256": {
+      "type": "string"
+    },
+    "manifestUrl": {
+      "type": "string"
+    },
+    "sourceRows": {
+      "type": "integer"
+    },
+    "sourceSha256": {
+      "type": "string"
+    },
+    "sourceUrl": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "canonicalUrl",
+    "manifestUrl",
+    "manifestSha256",
+    "integrityUrl",
+    "integritySha256",
+    "sourceUrl",
+    "sourceSha256",
+    "sourceRows",
+    "complete",
+    "blockObservationFromUtc",
+    "blockObservationToUtc",
+    "counts",
+    "coverage",
+    "attribution",
+    "accessNotes"
+  ],
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed2 schema fields changedSep 18, 2026
- addedOutput schema / properties / canonicalUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / dimensions / items / properties / canonicalUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
First observedSep 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish readOnly/destructive=false, so the bar is lower. The description still adds real behavioral context: source links expose full sign histories, portal blocks and cluster footprints, daily raw-source coverage includes legacy dates, and observations are historical rather than players/inventories/ownership. These are meaningful data-semantics caveats beyond the annotations.

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

Conciseness3/5

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

Information-dense but written as a run-on with three separate sentence groups, the longest being a bare list of sibling tool names. Front-loading is weak (the purpose sentence is the vaguest one) and the sibling enumeration could be tightened, though little is outright filler.

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?

An output schema exists, so return-value detail is not required, and the description covers sibling routing and data semantics well enough for a no-arg discovery tool. The main remaining gap is an explicit statement of what the primary dataset returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to clarify and schema coverage is moot; baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (NoCom dataset with complete-source manifests, checksums, native dimensions, map links) and distinguishes itself from get_nocom_daily_dataset, get_nocom_periods, and research_nocom_area. However, the opening phrase 'Discover NoCom World Pulse and Find data' is muddled and never states plainly what this dataset actually contains, so the core purpose stays slightly blurry.

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?

It explicitly routes the agent: use get_nocom_daily_dataset/get_nocom_daily_hits for exact UTC days, get_nocom_periods for fixed 30-day buckets, research_nocom_area for bounded synthesis, and the find_*/search_* tools for details. That is strong alternative-naming, though it never states when this tool itself is the right first choice versus those siblings.

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

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