Skip to main content
Glama
Sign In

bharatlas

by io.github.sathya-sankaran
OverviewDiscussionsAdmin

list_layers

Read-onlyIdempotent

List available geo layers. Use to discover what data bharatlas has. Returns layer IDs, names, row counts, categories, and download formats. Filter by category (boundaries, city-wards, environment, water, agriculture, transport, etc.), admin level (state, district, block, village, etc.), source, or text search.

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_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoText search across layer IDs, sources, and descriptions
levelNoFilter by admin level: state, district, subdistrict, block, village, etc.
limitNoMax results (default 20)
offsetNoSkip N results for pagination
sourceNoFilter by data source: LGD, SOI, Bhuvan, OpenCity, DataMeet, etc.
categoryNoFilter by category: boundaries, city-wards, people, environment, water, agriculture, transport, infrastructure, health-edu

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description usefully adds the return payload (IDs, names, row counts, categories, download formats), which matters because there is no output schema. It does not mention pagination defaults or result caps, which the schema covers only partially.

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?

Three short sentences, front-loaded with purpose then return shape then filtering. The filter sentence partially duplicates the schema, but it earns its place as a single scan-able summary of the query surface.

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 read-only discovery tool with no output schema, the description supplies both what comes back and how to narrow results, which is the essential information. Minor gaps are pagination expectations and whether filters combine as AND, but nothing critical is missing for correct invocation.

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 100%, so the schema already documents all six parameters. The description restates the filter dimensions and adds slightly richer category/level examples ("boundaries, city-wards, environment..."), but adds no syntax, combination rules, or default behavior beyond the schema.

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 and resource ("List available geo layers") and clarifies intent with "Use to discover what data bharatlas has." It is distinguishable from get_layer_detail/get_layer_schema/query_layer by being a discovery/listing operation, though it never names those siblings explicitly.

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 a clear usage context ("discover what data bharatlas has") that implies the browse-first workflow. It stops short of explicit when-not guidance or naming the alternative tools for drilling into a layer or querying its rows.

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

All bharatlas toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources