Skip to main content
Glama
bharatlas-mcp

bharatlas-mcp

create_map

Creates a data-collection map programmatically with custom fields, geometry, and AI photo modes, then auto-registers its admin link for managing contributions.

Instructions

Optional: create a collect map programmatically. Most maps are made online at collect.bharatlas.com (no key needed) — prefer that and register_map the link. This path needs COLLECT_API_KEY (the request-only anti-abuse gate) and auto-registers the new admin link.

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": {
      "name": "<name>",
      "purpose": "<purpose>",
      "geometry": "<geometry>",
      "fields": "<fields>"
    },
    "name": "create_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNohow people collect: form (default); form_ai = form plus notes a model writes from the photo, for the owner to check; photos_ai = people only take photos and the model fills the form (places only). AI modes need a photo field.
nameYes3-120 chars
fieldsYesthe form for each record (see collect.bharatlas.com/schema/v1.json); a field of type "photo" (max_photos 1-3) asks for photos
basemapNo
licenseNoopen licence id; default CC-BY-4.0
purposeYesshown to contributors
categoryNo
geometryYeswhat contributors may add
data_yearNo
moderationNodefault true — points wait for approval
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the key prerequisites: it requires COLLECT_API_KEY, that key is described as an anti-abuse gate, and the call has a side effect (auto-registers the new admin link). What it omits is the return payload and any failure/duplicate-name behavior for a mutating tool.

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, front-loaded with the discouraged path and followed by the prerequisites, so the agent hits the routing decision first. The "Optional:" prefix is slightly odd but costs little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter creation tool with no annotations and no output schema, the description covers routing, auth, and one side effect but says nothing about what is returned or how the mode/fields/geometry inputs interact beyond the photo requirement. Adequate, with clear gaps.

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 64%, and the description adds a genuine cross-parameter constraint the schema does not state: the AI modes (form_ai, photos_ai) require a photo field, and photos_ai is restricted to places. It still leaves basemap, category, data_year, and description entirely to the schema.

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?

States a specific verb and resource ("create a collect map programmatically") and immediately distinguishes it from the sibling path ("register_map the link"). An agent can tell which of the two map-creation routes applies without opening any schema.

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?

Gives an explicit preferred alternative (make the map online at collect.bharatlas.com, no key needed, then register_map) and the condition that selects this tool instead (programmatic creation with COLLECT_API_KEY). Both the when and the when-not are spelled out.

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