Skip to main content
Glama
bharatlas-mcp

bharatlas-mcp

publish

Submit approved points from a collect map to the bharatlas catalog for review; maintainer approval is required before they go live and become queryable.

Instructions

Submit a collect map's approved points to the bharatlas catalog for review (needs the admin link). Nothing goes live automatically — a maintainer approves the submission first; the response status is 'pending' until then. Once approved it is queryable via list_submissions / query_layer / locate above.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does substantial work: it discloses that nothing goes live automatically, that a maintainer must approve, that the returned status is 'pending', and that an admin link is required. It does not cover idempotency, re-submission behavior, or error conditions, which keeps it below a 5 for a mutation tool.

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, followed by the approval behavior and the post-approval retrieval path. No filler; every clause adds decision-relevant information.

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 one-parameter mutation with no annotations and no output schema, the description covers the essential lifecycle: prerequisite auth, review gating, response status, and downstream queryability. The gaps are secondary — what the response body contains beyond status and what happens on duplicate submissions.

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 0% and the single required parameter 'id' is undocumented in the schema. The description implicitly scopes it as the collect map's identifier via 'a collect map's approved points', which is useful disambiguation, but it never states the format, source, or that it is the map id rather than a layer or record id.

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?

The description names a specific verb and resource — submitting a collect map's approved points to the bharatlas catalog for review — and scopes it precisely enough to separate it from siblings like import_points, create_map, or moderate_record. It also states the outcome (pending, then queryable), so an agent understands the operation's role in the workflow.

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?

It gives a real prerequisite ('needs the admin link') and the trigger condition (points must already be approved on the collect map), plus pointers to the tools used after approval (list_submissions / query_layer / locate). It stops short of an explicit when-not-to-use or naming the alternative for the pre-approval path.

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