Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_searchplaceswithname

Search cities or places by name through the AstroChalit API to find location matches for Vedic astrology calculations.

Instructions

Execute searchPlacesWithName AstroChalit API

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": {
      "place": "<place>"
    },
    "name": "get_searchplaceswithname"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYesName of the city or place to search (at least 4 characters, e.g. 'Delhi', 'Mumbai')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It says nothing about what a lookup returns (place IDs, coordinates, timezone?), whether it is read-only, whether results are ranked or capped, or how errors are surfaced. A single opaque sentence is inadequate for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but shortness here reflects under-specification rather than economy: one sentence that conveys no actionable information. Nothing is front-loaded because nothing substantive is stated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter lookup tool this could be simple, but with no output schema and no annotations, the description should say at least what the search yields and how results are constrained. The critical question an agent would ask – what do I get back for a place name – is left unanswered.

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% and the single 'place' parameter is documented in the schema with a minimum-length rule and examples ('Delhi', 'Mumbai'). The description adds no meaning beyond that, so baseline 3 applies – the schema, not the description, does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description only restates the tool name in prose ('Execute searchPlacesWithName AstroChalit API'), adding no resource description beyond the identifier. An agent learns that it runs some API named searchPlacesWithName, but nothing about what it searches or returns. This is effectively tautology on the name.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisite, and no mention of any alternative among the ~30 sibling astrological tools. The only cue is the name itself, which the description merely echoes.

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

Deploy Server

Other Tools