Skip to main content
Glama
bharatlas-mcp

bharatlas-mcp

import_points

Bulk-import existing point records into a collect map using its admin link; require a named source and rights confirmation to preserve provenance for each row.

Instructions

Bulk-import points you already hold into a collect map (needs the admin link). NOT for synthetic data. Requires a named source + rights confirmation; each row lands with that source as its provenance.

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>",
      "records": "<records>",
      "source": "<source>",
      "rights_confirmed": "<rights_confirmed>"
    },
    "name": "import_points"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
sourceYes
recordsYesGeoJSON-like {geometry, properties}
rights_confirmedYesyou have the right to publish this under the map's licence

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose meaningful behavior: this is a bulk write, it requires admin-level access, it stamps provenance on every row, and it demands an explicit rights assertion. It omits failure semantics — partial-failure handling, duplicate behavior, row limits, or whether the import is atomic.

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?

Three short sentences, front-loaded with the action, then the exclusion, then the preconditions. No filler, and each clause adds a constraint the agent actually needs.

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?

For a 4-parameter bulk mutation with no annotations and no output schema, the definition covers purpose, auth, preconditions, and provenance semantics. The remaining gap is operational detail after the call — error/partial-failure behavior and what the import 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?

Schema coverage is only 50%, so the description compensates well: it explains that 'source' must be a named source and that its value becomes each record's provenance, and it ties the 'id' to the admin link. 'records' is left to the schema's GeoJSON-like hint, which is adequate.

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?

A specific verb + resource ("Bulk-import points ... into a collect map") makes the operation unmistakable and sets it apart from map-creation or single-record tools. The "NOT for synthetic data" clause further narrows the intent, though no sibling tool is named for the excluded case.

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?

Gives a real prerequisite ("needs the admin link") and an explicit exclusion ("NOT for synthetic data"), plus the preconditions for a valid call (named source + rights confirmation). It stops short of pointing to the tool an agent should use instead for synthetic data.

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