Skip to main content
Glama
bharatlas-mcp

bharatlas-mcp

get_map

Retrieve a map's metadata, record counts, and a link to open it in Collect for any registered scope by providing the map ID.

Instructions

A collect map's metadata + record counts, plus a link to open it in collect. Any registered scope.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe map (collection) id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the return payload (metadata + record counts + link), which is genuine value. It is silent on permission requirements, whether the link is time-limited, or cost of counting large maps, so key behavioral context is missing.

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?

Two tight sentences with the payload front-loaded; nothing is padding. The trailing fragment 'Any registered scope' is terse to the point of being cryptic, which keeps it from a top score.

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?

A simple one-parameter read tool with no output schema, and the description compensates by enumerating what comes back. The main open question an agent might have — what 'registered scope' means and what permissions apply — is left unresolved.

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?

Single required parameter with 100% schema description coverage ('the map (collection) id'), so the schema already does the work. The description adds no format or sourcing detail for the id beyond implying it identifies the map.

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?

Names the resource (a collect map) and specifies exactly what is retrieved: metadata, record counts, and an open-in-collect link. That is concrete enough to distinguish it from siblings like get_records, get_layer_detail, or list_my_maps, though it never contrasts itself with them explicitly.

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

Usage Guidelines2/5

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

No when-to-use / when-not-to-use guidance and no alternative named. The only hint is 'Any registered scope', which gestures at applicability but doesn't tell an agent when to pick this over list_my_maps or get_records.

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