Skip to main content
Glama
bharatlas-mcp

bharatlas-mcp

get_records

Collect a map's records as a GeoJSON FeatureCollection for reading, analysis, or backup/export, with optional status filtering for admins.

Instructions

A collect map's records as a GeoJSON FeatureCollection — for reading, analysis, or backup/export. view and collect scope return published points; admin can also read pending/rejected via status. Each record's properties._photos lists its photo links (public once the point is approved); _ai holds notes a model wrote from the photo (others see only notes the owner accepted).

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_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
statusNoadmin only: pending | published | rejected

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses that view/collect scopes return only published points while admin scope can read pending/rejected, and it explains per-record visibility rules for _photos (public only once approved) and _ai (only owner-accepted notes visible to others). It omits operational traits such as result limits, pagination, or behavior for an unknown id.

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?

Three sentences, purpose front-loaded, with scope rules and field semantics following in priority order. The _photos/_ai sentence is dense but earns its place given there is no output schema; no filler wording.

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?

No output schema exists, so the description must describe the return value — it does so concretely (FeatureCollection with properties._photos and _ai). Scope-based access behavior is covered; only edge cases like pagination, ordering, or empty/invalid-id handling are missing, which are minor for a read tool.

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 50%: `status` is documented in the schema and the description only restates its admin-only pending/rejected role, adding no new syntax. The required `id` is never explicitly characterized as the collect map identifier, though 'a collect map's records' implies it; the _photos/_ai detail describes output fields rather than parameters.

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?

States a specific verb and resource ('collect map's records') plus the concrete return shape (GeoJSON FeatureCollection), so the agent knows exactly what it gets back. It does not name any sibling (e.g. query_layer or nearby) to distinguish this retrieval path from alternative ones.

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

Usage Guidelines3/5

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

The phrase 'for reading, analysis, or backup/export' gives loose use-case context, and the scope sentence implies when admin status filtering applies. However, it never states when NOT to use this tool or which sibling to prefer for filtered or proximity queries, leaving selection to inference.

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