Skip to main content
Glama
Céu Natal

Céu Natal

Progressões secundárias

calcular_progressoes
Read-onlyIdempotent

Calculates secondary progressions (one day equals one year) from a natal chart to a target date, returning progressed planets, aspects, Moon/Sun emphasis, and sign ingresses.

Instructions

Calcula as progressões secundárias (técnica 'um dia = um ano') de um mapa natal para uma data alvo. Retorna posições progredidas, aspectos entre planetas progredidos e natais, destaque para Lua progredida (fase emocional atual, ~2.5 anos por signo), Sol progredido (capítulo de vida, ~30 anos por signo), e sinaliza ingressos recentes e mudanças iminentes de signo.

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_alvo": "<data_alvo>"
    },
    "name": "calcular_progressoes"
  }
}

Input Schema

NameRequiredDescriptionDefault
natalYes
data_alvoYesData alvo (presente/futuro) no formato DD/MM/YYYY.
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 observedv2.2.6

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive calculation. Beyond that, the description adds useful behavioral context by explaining what the result includes: progressed positions, aspects to natal planets, emphasized progressed Moon and Sun, and flags for recent or imminent sign ingresses.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded with the core calculation and then summarizes the return content in a compact, purposeful list. The parenthetical explanations for the progressed Moon and Sun add domain clarity without unnecessary wording.

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 calculation tool with no output schema, the description does a good job explaining the kinds of results returned. It does not detail output formatting or edge cases such as missing birth time, but the essential behavior and result scope are covered adequately.

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?

The description references a natal chart and a target date, but it does not add meaning beyond the schema for the nested natal object or the house-system enum. With 67% schema description coverage and detailed field descriptions already present, the schema carries most of the parameter clarification.

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 verb and resource: 'Calcula as progressões secundárias' for a natal chart and target date. It also identifies the technique ('um dia = um ano') and distinguishes this operation from unrelated sibling calculations such as transits or solar returns.

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?

The description implies the tool is used when secondary progressions are desired for a natal chart and target date. However, it does not explicitly state when to choose this over sibling techniques like transits, solar revolutions, or synastry, leaving selection guidance implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.