Skip to main content
Glama
bharatlas-mcp

bharatlas-mcp

list_my_maps

Lists locally registered collect maps and their scopes so you can review what is stored before querying or managing your maps.

Instructions

List the collect maps you have registered here (local store), each with its scope.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_my_maps"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. "List" reliably signals a non-mutating read and the local-store scope is useful behavioral context, but it says nothing about ordering, completeness, or failure behavior when nothing is registered.

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?

A single sentence with the subject and the distinguishing scope qualifier front-loaded; no filler. It loses a point only because "collect maps" and "scope" are undefined jargon that a first-time caller must guess at.

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 parameterless listing tool with no output schema, the description is close to sufficient, and "each with its scope" gestures at the return shape. It still leaves "scope" undefined and does not indicate whether the list is paginated or how large it may be, which matters since no output schema documents the response.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline of 4 applies. Nothing in the description misdescribes the input surface.

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?

The description gives a specific verb and resource ("List the collect maps") and constrains scope to those "you have registered here (local store)." That local-store qualifier loosely separates it from server-facing siblings like get_map or list_submissions, but no sibling is named, so the differentiation is inferential rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The "(local store)" parenthetical implies this is the tool for enumerating maps you previously registered, which is usable guidance. However, it never states when to prefer this over get_map, query_layer, or the other list_* tools, and gives no exclusions or prerequisites.

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