2b2t Atlas

get_nocom_dataset

Read-only

Discover Nocom World Pulse aggregates and the complete-source Find release. The find field includes counts, native dimension coverage, canonical/source URLs, query API URLs and immutable JSON manifest. Start with research_nocom_area for a bounded area synthesis; use find_nocom_storage, search_nocom_signs and find_nocom_portals for targeted queries; use sourceJsonUrl for full sign history. This tool returns metadata. Observations are historical, not players, current inventories or ownership; aggregate coverage begins March 2020, not 2018.

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
`periodLayerCount`	Yes
`exploitPatchedDate`	Yes
`groupedServerScope`	Yes
`highwaySourceScope`	Yes
`groupedSourceSha256`	Yes
`highwaySourceSha256`	Yes
`tilesGeneratedAtUtc`	Yes
`highwayActivityApiUrl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful caveats: observations are historical rather than live player/inventory/ownership data, aggregate coverage starts March 2020 not 2018, and the JSON manifest is immutable. These non-obvious behavioral facts go well beyond the structured 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?

The description is compact and front-loaded with purpose, but the middle sentence crowds multiple sibling alternatives and field details into one long clause. Every sentence contributes value, though the flow could be cleaner.

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?

Given zero parameters, existing annotations, and an output schema, the description fully covers what an agent needs: what the tool returns, how it differs from siblings, important historical-data caveats, and the coverage start date. Nothing essential is missing.

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 has zero parameters and the schema is empty, so there are no parameter semantics to document. The description's mention of fields like sourceJsonUrl relates to the response, not invocation parameters, which is acceptable given the baseline for 0-param tools.

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?

The description states a specific resource (Nocom World Pulse aggregates / Find release), says the tool returns metadata, and enumerates what the find field contains. It also disambiguates from siblings by directing targeted queries to find_nocom_storage, search_nocom_signs, and find_nocom_portals.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly gives routing guidance: start with research_nocom_area for bounded area synthesis, use specific siblings for targeted queries, and use sourceJsonUrl for full sign history. This tells an agent when this tool is appropriate versus when to choose another.

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.