Skip to main content
Glama

AstroLogics

Search birth place

search_birth_place
Read-onlyIdempotent

Resolve a place name to coordinates for use as the birth place of a Vedic chart. Call this first when the user gives a place name rather than latitude and longitude.

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": {
      "q": "<q>"
    },
    "name": "search_birth_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesPlace name, for example "Noida" or "Darbhanga, Bihar".
countryNoOptional country preference such as "in". Matching widens automatically when that country has no result.

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 cover read-only, idempotent, non-destructive behavior, so the description's contribution is the workflow ordering ('call this first'), which is genuinely useful sequencing context not present in structured fields. It stops short of saying what happens on no-match, though openWorldHint=false hints at a bounded place database.

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?

Two sentences, front-loaded with purpose before the call-ordering hint, with no filler. Slightly terse given that search failure behavior goes unaddressed.

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 two-parameter, annotation-covered lookup tool with no output schema, the description supplies purpose, expected return (coordinates), and invocation ordering. Only the no-result behavior is left implicit.

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 schema itself documents both q (with examples) and the country fallback widening. The description adds no parameter-level meaning beyond the schema, so baseline 3 applies.

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 (resolve a place name to coordinates) and scopes it to a concrete use case, the birth place of a Vedic chart. No sibling tool does geocoding, so the agent can distinguish it immediately from get_birth_chart and the rest.

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?

Gives an explicit trigger ('Call this first when the user gives a place name') and the contrasting condition ('rather than latitude and longitude') that selects the alternative input path. The when and when-not are both 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources