Skip to main content
Glama

NatalChart.AI Astrology

Best cities for a chart

best_cities
Read-onlyIdempotent

The catalogue of major cities ranked for one chart, overall or by chosen life spheres, worldwide or in one region. (Premium or MAX) Use it when the user asks where in the world to live, work or travel; it ranks major cities, optionally by life sphere or region.

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": {
      "birth": "<birth>"
    },
    "name": "best_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault
birthYes
focusNo
limitNo
regionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and purity are covered. The description's real addition is the "(Premium or MAX)" plan-gating note, which is genuinely non-obvious, but it says nothing about ordering of results, tie-breaking, or what the ranking is based on beyond "life spheres".

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 tight sentences with the capability stated first and the usage trigger second; nothing is wasted. The "(Premium or MAX)" parenthetical is inserted mid-sentence and reads awkwardly, slightly hurting flow.

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

Completeness3/5

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

This is a nested-input, chart-derived tool with no output schema, and the description never hints at the return shape (a ranked list of N cities) or how the required birth chart drives the ranking. It also leaves the location_score sibling undifferentiated, so an agent has to open the schema to resolve both questions.

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?

Top-level schema description coverage is 0%, and the description only loosely maps to two of the four parameters: "life spheres" implies focus (identity/love/body/money/home/mind) and "one region" implies region. Neither the limit parameter nor the required birth object is mentioned, so the description only partially compensates for the coverage gap.

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

Purpose4/5

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

States a concrete resource (major cities) and what it produces (a ranked catalogue for one chart), scoped to overall or per-life-sphere and worldwide or regional. An agent can tell this is a ranking tool, though it never distinguishes itself from the sibling location_score, which sounds like it covers similar ground.

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?

"Use it when the user asks where in the world to live, work or travel" gives a clear triggering condition, and the scope clauses reinforce it. It stops short of exclusions or naming an alternative (location_score, best_days) for adjacent questions, so it is clear context rather than full routing guidance.

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