Skip to main content
Glama

Revolução lunar

calcular_revolucao_lunar
Read-onlyIdempotent

Calcula a revolução lunar (lunar return) — o mapa do instante exato em que a Lua retorna à longitude que ocupava no nascimento, técnica de previsão mensal com ciclo de ~27,3 dias. Retorna o primeiro retorno lunar a partir da data de referência informada, com mapa completo, aspectos com o natal, sobreposição dos dois mapas e destaques centrados na Lua: casa que ela ocupa, ascendente da revolução e seus regentes, planetas angulares. Exige hora e local de nascimento. O parâmetro local_revolucao é obrigatório.

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_referencia": "<data_referencia>",
      "local_revolucao": "<local_revolucao>"
    },
    "name": "calcular_revolucao_lunar"
  }
}

Input Schema

NameRequiredDescriptionDefault
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).
data_referenciaYesData DD/MM/YYYY a partir da qual buscar o retorno. Devolve o PRÓXIMO retorno — o primeiro que ocorra nessa data ou depois dela — e não o ciclo já em curso. Passar a data de hoje costuma devolver o mês lunar que ainda vai começar; nesse caso o resultado traz o bloco `ciclo_em_curso` com a data para obter o ciclo vigente.
local_revolucaoYesCidade e UF/país onde a pessoa estará no momento do retorno. Obrigatório — muda apenas os ângulos e as casas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds real semantics: it returns the FIRST return on or after the reference date rather than the cycle already running, and it discloses the `ciclo_em_curso` block emitted in that case. It also explains that local_revolucao shifts only angles and houses, which is behavioral context an agent needs to interpret a result.

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?

Front-loaded with the definition, then the return-content, then prerequisites — a logical order with no filler sentences. Slight redundancy between the closing "Exige hora e local de nascimento" and the schema's own "Obrigatória na prática" markers, but each sentence still carries useful information.

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

Completeness5/5

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

There is no output schema, and the description compensates by enumerating the returned content: the full chart, aspects to the natal, the double-map overlay, and Moon-centered highlights (occupying house, revolution ascendant and rulers, angular planets). Combined with the prerequisite and next-return semantics, an agent has enough to call and interpret the tool despite the nested 4-parameter schema.

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 75%, so the schema already documents data, hora, local, sistema_casas and local_revolucao in detail. The description mainly restates the practical obligatoriness of birth time/place and the mandatory status of local_revolucao — both already present in the schema — adding little new syntax or semantics.

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?

Names a specific verb and resource ("Calcula a revolução lunar") and immediately defines the technique — the chart for the instant the Moon returns to its natal longitude, a ~27.3-day monthly cycle — plus the exact scope (first return on or after the reference date). An agent can distinguish this from calcular_revolucao_solar purely from the text, without opening the 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?

Establishes the usage context (monthly forecasting technique), a prerequisite ("Exige hora e local de nascimento"), and a concrete operational rule for date_referencia — pass today's date and you usually get the upcoming lunar month. It does not explicitly name the solar-return sibling as the alternative for annual forecasting or state when not to use this tool, so it stops short of 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.