Skip to main content
Glama

NatalChart.AI Astrology

Astrocartography for one place

location_score
Read-onlyIdempotent

One place against one chart: the relocated angles, the planets on them with orbs, a score for each life sphere and an overall score. (Premium or MAX) Use it when the user asks whether a specific city or place suits them; it needs a birth time and the place's coordinates.

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>",
      "location": "<location>"
    },
    "name": "location_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
birthYes
locationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safe-read profile (readOnlyHint, idempotentHint, closed-world), and the description adds genuinely new context: the '(Premium or MAX)' plan gate and the fact that a birth time is needed. The remaining gap is that 'it needs a birth time' conflicts slightly with the schema, where time is nullable and results are merely withheld — an agent could wrongly refuse a no-time request.

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 dense sentences that lead with the deliverable, then the triggering condition and prerequisites — no filler. The output enumeration is long but each element is informative, and the parenthetical plan tier is compact.

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 nested-input tool with no output schema, the description adequately covers what is returned, when to invoke it, and the access tier. The null-birth-time case and the relationship to best_cities are the only notable omissions.

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 reported at 0% despite nested objects, so the description carries the burden — and it only mentions 'birth time' and 'the place's coordinates.' It never clarifies that the birth bundle itself requires coordinates and a date, nor the optional timezone resolution, leaving half the nested structure to be discovered in the schema.

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?

It names a specific verb-like operation and enumerates the concrete outputs (relocated angles, planets with orbs, per-sphere and overall scores), so an agent knows exactly what it gets. 'One place against one chart' implicitly contrasts with the multi-place sibling best_cities, but that sibling is never named, so the differentiation is inferred rather than stated.

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 whether a specific city or place suits them' gives a clear triggering condition, and the prerequisites (birth time, place coordinates) are spelled out. There is no explicit exclusion or pointer to best_cities for comparing several places, which is the main missing piece.

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