Skip to main content
Glama
bharatlas-mcp

bharatlas-mcp

register_map

Register a collect.bharatlas.com share link so this server can act on an existing map, with the #fragment token setting admin, collect, or view access.

Instructions

Register a collect map so this server can act on it. Paste the whole share link (e.g. https://collect.bharatlas.com/c//admin#). The token in the #fragment sets your scope: admin = full control, collect = add points, view = read published. New maps are created online at collect.bharatlas.com first (no account or key needed); this registers one you already made.

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": {
      "link": "<link>"
    },
    "name": "register_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesa collect.bharatlas.com share link with the token in the #fragment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does real work: the #fragment token determines permission scope, with admin = full control, collect = add points, view = read published. That is a genuine authorization model an agent needs. It still omits what registration returns, whether re-registering an existing link is idempotent, or how an invalid/expired token fails.

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?

Four short sentences, front-loaded with the action, then the input format, then the permission semantics, then the creation-vs-registration distinction. No filler and no repetition of the title or schema.

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

Completeness5/5

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

For a single-parameter, no-annotation, no-output-schema tool, the description covers purpose, exact input format, permission consequences, and prerequisites. The only real gap is the return value, but the success outcome (the server can now act on the map) is implied clearly enough for selection and invocation.

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 100%, so the baseline is 3, but the description adds genuine meaning: paste the whole share link, with a concrete example URL showing where the id and #token sit, and an explanation that the fragment token dictates subsequent capability. That converts a bare string parameter into an understood credential.

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 ('Register a collect map') plus the scope of what it enables ('so this server can act on it'). It also draws a sharp line between registering an existing map and making a new one ('New maps are created online at collect.bharatlas.com first ... this registers one you already made'), which separates it from a create-style sibling.

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 clear when-to-use context: the user already has a share link and a map that exists on the hosted site, and no account or key is required for creation. It implies the exclusion (don't use this to create a map) without naming an alternative tool, so guidance is strong but not a full when/when-not/alternative triad.

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