Skip to main content
Glama
bharatlas-mcp

bharatlas-mcp

edit_map

Update a collect map's name, description, purpose, category, data year, or basemap using the admin link. Change the licence only while the map holds no records.

Instructions

Edit a collect map's settings: name/description/purpose/category/data_year/basemap (needs the admin link). Licence can only change while the map has no records.

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": "edit_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameNo
basemapNo
licenseNo
purposeNo
categoryNo
data_yearNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does add real behavioral context — an admin-link prerequisite and a state-dependent restriction on licence changes — but says nothing about how omitted fields are treated, whether edits are reversible, or what the call returns.

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?

Two compact sentences with the mutable field list front-loaded and the conditional caveat trailing as an exception. No filler and no repetition of the tool name.

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 a mutation tool with no annotations, no output schema, and zero schema-description coverage, the definition covers the surface fields and one important constraint but omits the required id semantics, permissions model, and the effect of the call on existing map data.

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 0% across 8 parameters, so the description must compensate. It does name and give meaning to most of them (name, description, purpose, category, data_year, basemap, license) plus a license-specific precondition, but leaves the required 'id' parameter entirely unexplained and gives no formats or accepted values.

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 ('Edit') and resource ('a collect map's settings') and enumerates the editable fields: name/description/purpose/category/data_year/basemap. An agent can distinguish it from get_map or create_map by the mutation framing, though it does not name any sibling 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?

There is no guidance on when to choose this tool over alternatives such as create_map or register_map, and no statement of who may call it beyond the parenthetical 'needs the admin link'. The only conditional rule given ('Licence can only change while the map has no records') is a per-field constraint, not when-to-use guidance.

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