Skip to main content
Glama

Revolução solar

calcular_revolucao_solar
Read-onlyIdempotent

Calcula a revolução solar (solar return) de um ano — o mapa do instante exato em que o Sol retorna à longitude que ocupava no nascimento, técnica de previsão anual. Rege o período até a revolução seguinte. Retorna o mapa completo da revolução (planetas, casas, ângulos, aspectos internos), os aspectos entre a revolução e o mapa natal, a sobreposição dos dois mapas e destaques da leitura: ascendente da revolução e seus regentes, casa ocupada pelo Sol e planetas angulares. Exige hora e local de nascimento. O parâmetro local_revolucao é obrigatório e define ascendente, meio do céu e casas — as posições planetárias são as mesmas em qualquer lugar do mundo.

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>",
      "ano": "<ano>",
      "local_revolucao": "<local_revolucao>"
    },
    "name": "calcular_revolucao_solar"
  }
}

Input Schema

NameRequiredDescriptionDefault
anoYesAno da revolução (1800–2200, nunca anterior ao nascimento). É o retorno que ocorre em torno da data de nascimento nesse ano — pode cair um dia antes ou depois do aniversário, e para quem nasceu no começo de janeiro pode cair em dezembro do ano anterior. Vale até o retorno seguinte, então para saber qual rege hoje use o ano do último aniversário.
natalYes
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_revolucaoYesCidade e UF/país onde a pessoa estará no momento do retorno (ex: 'Lisboa, Portugal'). Obrigatório — muda apenas os ângulos e as casas, nunca as posições planetárias.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, so the bar is lower, and the description still adds real context: the birth-time/place prerequisite, the scope of the returned chart (planets, houses, angles, internal aspects, natal cross-aspects, overlay, highlights), and the key fact that local_revolucao moves only angles and houses. It does not describe failure behavior when time or place is missing beyond calling them 'obrigatória na prática'.

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?

It is front-loaded: purpose and predictive scope come first, then return contents, then prerequisites and the local_revolucao caveat. It is long, and the closing sentence partially duplicates the schema's own explanation of local_revolucao, so a little trimming is possible 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 carries the burden of describing results and does so thoroughly, and it covers the practically required birth time and place. What remains unstated is what happens on invalid or incomplete input (e.g., missing hora/local) and the exact shape of the response, which matters for a nested four-parameter tool.

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 coverage is 75% and the input schema already documents ano's edge cases and local_revolucao's effect on angles/houses in detail, so the schema does the heavy lifting. The description restates that local_revolucao is mandatory and changes only angles and houses — the same claim already in the schema — adding emphasis rather than new meaning.

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 names a specific technique (solar return: the chart of the instant the Sun returns to its natal longitude) and explains its annual predictive role, which unambiguously separates it from siblings like calcular_revolucao_lunar and calcular_transitos. It also enumerates what the tool produces, so an agent knows both the verb and the artifact.

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 states prerequisites plainly ('Exige hora e local de nascimento') and gives genuine usage guidance for the year parameter — use the year of the last birthday to know which revolution governs today, with the caveat about returns falling a day before/after the birthday. It does not explicitly contrast itself with progressions or transits, so it stops short of full when/when-not 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.