2b2t Atlas

research_location

Read-only

Research a place by name or search phrase: returns the best full record, alternate candidates, nearby places and relationships. Exact homonyms return candidate IDs instead of guessing. For only a known ID use get_location; for discovery lists use search_locations; for coordinate-based context use research_area.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Location name or distinctive search phrase.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`location`	Yes
`evidenceNotice`	Yes
`nearbyLocations`	Yes
`searchCandidates`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 21, 2026
- addedOutput schema / properties / location / properties / dateAddedRecorded
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / location / properties / modifiedRecorded
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed2 schema fields changedSep 20, 2026
- addedOutput schema / properties / location / properties / renders / items / properties / captureDatePrecision
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / location / properties / warps / items / properties / captureDatePrecision
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed2 schema fields changedSep 20, 2026
- addedOutput schema / properties / location / properties / renders / items / properties / blueMapProfile
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / location / properties / renders / items / properties / blueMapUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed2 schema fields changedSep 18, 2026
- addedOutput schema / properties / location / properties / renders / items / properties / locationCanonicalUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / location / properties / warps / items / properties / locationCanonicalUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
First observedSep 14, 2026

TDQS

A4.7/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 behavioral context beyond that: it returns alternate candidates, nearby places, relationships, and handles exact homonyms by returning candidate IDs instead of making a guess. This gives the agent a concrete model of what the tool will do without relying solely on the output schema.

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

Conciseness5/5

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

The description is three efficient sentences: the first states the operation and return value, the second covers the homonym edge case, and the third provides sibling routing. Every sentence earns its place and the key behavior is front-loaded.

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?

For a single-parameter read tool with a rich description, complete sibling routing, and an output schema, nothing essential is missing. The description covers purpose, alternatives, and edge-case behavior, and the output schema handles return-value details.

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 description coverage is 100%: the schema already defines 'name' as 'Location name or distinctive search phrase.' The description repeats this idea with 'by name or search phrase' and adds behavioral context, but it does not add meaningful parameter-level detail beyond the schema, so the baseline of 3 is appropriate.

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 verb and resource: 'Research a place by name or search phrase', and defines the return contents: 'best full record, alternate candidates, nearby places and relationships'. It also differentiates from siblings by naming get_location, search_locations, and research_area as the alternatives, so an agent can select it confidently.

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 gives explicit routing guidance: use get_location for a known ID, search_locations for discovery lists, and research_area for coordinate-based context. It also notes the homonym edge case, telling the agent that exact homonyms return candidate IDs instead of guessing. This is clear when-to-use and when-not-to-use guidance.

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.