Skip to main content
Glama
Sign In

Spatial India

by com.spatialindia
OverviewDiscussionsAdmin

Find an indicator

find_indicator
Read-only

Use FIRST, before any other tool, whenever a question names a subject rather than an indicator id — "stunting", "land inequality", "bank credit". Returns matching indicator ids with their unit, source, vintage, caveat and district coverage. Every other tool needs an id from here; ids are not guessable and inventing one fails.

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": {
      "query": "<query>"
    },
    "name": "find_indicator"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPlain words describing the subject. Every word must appear somewhere in the indicator — prefer two or three words ("child stunting", "land inequality") over a sentence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only behavior, and the description adds useful behavioral detail: it returns matching ids plus unit, source, vintage, caveat, and district coverage, and warns that non-existent ids fail. This goes beyond the structured annotations without contradicting them.

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?

The description is three sentences, front-loads the most critical instruction ('Use FIRST, before any other tool'), and includes concrete examples. Every sentence earns its place: when to use, what it returns, and why this step is mandatory.

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 lookup tool with no output schema, the description is complete: it explains the entry-point role, the input nature, the returned fields, and the failure mode. An agent has enough context to invoke it correctly without additional documentation.

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 100%, with the query parameter already well-documented as plain words and guidance to prefer two or three words. The description reinforces the subject-based nature of the query but does not add substantial new parameter meaning beyond the schema, so the baseline of 3 is appropriate.

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 ('find') and resource ('indicator'), and makes the scope unmistakable: it resolves a subject phrase to indicator ids. It also distinguishes itself from all sibling tools by stating that every other tool needs an id from here, so an agent can confidently choose it as the entry point.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance: 'Use FIRST, before any other tool, whenever a question names a subject rather than an indicator id.' It also says ids are not guessable and inventing one fails, which effectively tells the agent not to skip this step and to avoid fabricating ids.

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

All Spatial India 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