Skip to main content
Glama

Mapa natal

calcular_mapa_natal
Read-onlyIdempotent

Calcula o mapa astral natal completo de uma pessoa. Retorna posições planetárias, casas (Placidus por padrão; sistema configurável), ângulos, aspectos entre planetas, pontos sensíveis (nodos verdadeiros e Quíron) e síntese (elementos, qualidades, hemisférios, stelliums). Se hora ou local forem omitidos, retorna apenas posições por signo, sem casas nem ângulos. Sem hora, o cálculo usa 12:00 no horário local e a Lua vem marcada como incerta (posicao_incerta, signo_pode_mudar).

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": {
      "data": "<data>"
    },
    "name": "calcular_mapa_natal"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesData de nascimento no formato DD/MM/YYYY.
horaNoHora de nascimento no formato HH:MM. Opcional; sem ela, usa 12:00 local.
nomeNoNome da pessoa (apenas para identificação). Opcional.
localNoCidade e UF/país (ex: 'Belo Horizonte, MG'). Opcional.
is_dstNoSó para hora ambígua ou inexistente na transição do horário de verão: true = horário de verão, false = horário padrão.
sistema_casasNoSistema de casas: P (Placidus, default), K (Koch), W (Whole Sign), E (Equal), R (Regiomontanus), C (Campanus), O (Porphyrius), B (Alcabitus), M (Morinus), T (Topocentric).

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 and destructiveHint=false, so the safety profile is covered. The description goes well beyond that by disclosing the degraded-output mode and the concrete fallback rule (12:00 local, Moon flagged as posicao_incerta/signo_pode_mudar) — a real behavioral trait an agent could not infer otherwise.

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?

Three sentences, front-loaded with purpose followed by the return payload and then the conditional caveat; no filler or restatement of the title. The middle enumeration is dense but each item is a distinct output the caller may need, so little could be cut without losing information.

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?

With no output schema, the description does the necessary work of describing return contents and the degraded variant, covering what an agent needs before calling. Only minor gaps remain, such as error behavior for invalid dates and confirmation of whether 'nome' affects anything beyond labelling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so formats (DD/MM/YYYY, HH:MM) and the house-system enum are already documented; the baseline would be 3. The description earns a bump by explaining the consequence of omitting hora and local rather than just their syntax, which is genuine semantic added value beyond the schema.

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?

The description opens with a specific verb and resource ('Calcula o mapa astral natal completo de uma pessoa') and then enumerates the exact outputs: planetary positions, houses, angles, aspects, sensitive points and synthesis. That scope is intrinsically distinct from the siblings (composite chart, synastry, transits, progressions), so an agent can tell which tool to pick without inspecting a schema.

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?

It clearly states the operative condition — what happens when hora or local are omitted (sign-only positions, no houses or angles) — which is the main decision an agent must make before calling. It does not, however, route the agent to alternatives such as calcular_sinastria or calcular_mapa_composto, so sibling selection still depends on the resource name alone.

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.