Skip to main content
Glama

Moon Dasha Vedic Astrology

Find a place

find_place
Read-onlyIdempotent

Look up a birthplace or event place in Moon Dasha's place data and get its place_id, coordinates and IANA time zone. Every Moon Dasha calculation that needs a place takes it as this place_id. Up to five matches, best first.

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

Input Schema

NameRequiredDescriptionDefault
queryYesThe place name, optionally followed by its state or country: "Jaipur", "Springfield Illinois", "Paris France".

Output Schema

NameRequiredDescriptionDefault
placesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, and the description is consistent with that closed dataset ('Moon Dasha's place data'). It adds real behavior beyond them: a hard cap ('up to five matches'), ranked ordering ('best first'), and the downstream contract that place_id is the required key for calculations.

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 lookup action and its outputs, then the downstream contract, then the result limit. No filler and nothing repeated from the title.

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?

An output schema exists, so return values needn't be re-explained, and annotations cover the safety profile for a single read-only parameter tool. The description fills the remaining gaps an agent needs: result count, ranking, and the place_id handoff to calculation tools.

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% and the query parameter already documents the 'name plus state or country' format with examples, so the description adds little parameter-level syntax. It only reinforces the semantic scope as 'birthplace or event place', which is the expected baseline-3 level when the schema does the heavy lifting.

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 ('look up a birthplace or event place in Moon Dasha's place data') and names the concrete outputs (place_id, coordinates, IANA time zone). The 'place_id' framing distinguishes it clearly from every calculation sibling that consumes that id.

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?

'Every Moon Dasha calculation that needs a place takes it as this place_id' tells the agent exactly when this tool must be called first, which is the key routing decision. It does not state any when-not condition or name a competing lookup, so it falls short of a full alternative-aware 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources