Skip to main content
Glama

Trânsitos

calcular_transitos
Read-onlyIdempotent

Calcula os trânsitos planetários para uma data específica em relação a um mapa natal. Retorna a posição atual dos planetas, aspectos entre planetas em trânsito e planetas natais (com aplicando/separando), em qual casa natal cada planeta em trânsito está caindo, e síntese com destaque para trânsitos de planetas lentos (Saturno, Urano, Netuno, Plutão e Quíron) com orbe < 2°.

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": {
      "natal": "<natal>",
      "data_transito": "<data_transito>"
    },
    "name": "calcular_transitos"
  }
}

Input Schema

NameRequiredDescriptionDefault
natalYes
data_transitoYesData do trânsito no formato DD/MM/YYYY.
hora_transitoNoHora HH:MM. Default 12:00 UTC se omitida.
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).
local_transitoNoLocal de observação. Default Greenwich/UTC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description earns credit for disclosing output content (positions, applying/separating aspects, natal house placements, slow-planet emphasis with orb < 2°), but says nothing about cost, timing, or failure modes for invalid dates or ambiguous birth times.

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?

A single front-loaded sentence that leads with the verb and resource, then enumerates the returned components. Every clause carries information about the result set; no filler or repetition of the title.

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 carries the burden of describing returns and does so with concrete detail on aspects, houses and slow-planet orbs. For a 5-parameter tool with a nested natal object, the remaining gaps (error behavior, computed ephemeris source) are minor.

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 80%, so the schema already documents the natal sub-fields, date formats, the HH:MM default of 12:00 UTC and the house-system enum. The description adds no parameter-level meaning beyond what structured data provides, so the baseline 3 applies.

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 specific verb and resource ('Calcula os trânsitos planetários') and pins the scope to 'uma data específica em relação a um mapa natal', which implicitly separates it from calcular_mapa_natal (which builds the chart) and calcular_progressoes. It stops short of naming any sibling or explicitly contrasting behavior, so a 4 rather than a 5.

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

Usage Guidelines3/5

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

Usage is implied by the requirement of an existing natal map plus a transit date, which tells an agent the precondition. There is no explicit when-to-use/when-not statement and no guidance on choosing between this and progressões, sinastria or revolução solar.

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.