Skip to main content
Glama
Sign In

mugilu

by io.github.sathya-sankaran
OverviewDiscussionsAdmin

search_place

Read-onlyIdempotent

Resolve an Indian place name to candidates (name, detail, coordinate). Use to disambiguate before conditions_at. Covers cities, districts and air-monitoring stations. For sub-city wards, hospitals, forests, rivers or boundaries, use a geo source like the bharatlas MCP instead.

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

Input Schema

NameRequiredDescriptionDefault
queryYesA place name or partial name in India.

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 readOnly, openWorld and idempotent, so safety is covered. The description still adds real behavioral value by signalling that it returns multiple candidates rather than a single authoritative match, and by bounding resolution scope to cities, districts and monitoring stations. It omits result limits or ranking/pagination behavior, which keeps it below a 5.

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 core purpose, then the sequencing rule, then the exclusion. Every sentence earns its place and nothing is repeated from the 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 one-parameter lookup with no output schema, the description is complete: it states what comes back (name, detail, coordinate), the coverage domain, the intended workflow position before conditions_at, and where to go for out-of-scope geography.

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% with a single documented parameter, so the baseline of 3 applies. The description adds no format or matching semantics (e.g. alias handling, minimum query length) beyond what the schema's "place name or partial name" already states.

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?

Specific verb ("Resolve") plus resource ("Indian place name") plus the shape of the result (name, detail, coordinate). It also carves out the exact domain it covers — cities, districts and air-monitoring stations — so an agent can tell instantly whether this tool applies.

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?

Explicit when-to-use ("disambiguate before conditions_at") and explicit when-not with a named alternative for sub-city features (bharatlas MCP). Both the sequencing rule and the exclusion are stated, leaving nothing to inference.

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

All mugilu 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