Skip to main content
Glama

Mapa composto

calcular_mapa_composto
Read-onlyIdempotent

Calcula o mapa composto (composite chart) de duas pessoas pelo método de midpoints — o mapa da 'relação como entidade'. Diferente da sinastria, que compara dois mapas, o composto cria um terceiro mapa a partir dos pontos médios das longitudes planetárias. Retorna posições compostas, ângulos (ASC e MC compostos quando ambas as pessoas têm hora+local), aspectos internos do composto e síntese de elementos. Não retorna casas — composto por midpoint não tem instante/local definidos.

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": {
      "pessoa_a": "<pessoa_a>",
      "pessoa_b": "<pessoa_b>"
    },
    "name": "calcular_mapa_composto"
  }
}

Input Schema

NameRequiredDescriptionDefault
pessoa_aYes
pessoa_bYes
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.2/5.0
Behavior4/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, and the description still adds meaningful behavior: the conditional that ASC/MC are only computed when both people have hora+local, and the explicit limitation that no houses are returned and why. It does not mention error behavior for missing/invalid data or how ambiguous DST input is handled.

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 core action and method, then the sibling contrast, then the return contract and the limitation. Dense and mostly waste-free; the quoted 'relação como entidade' framing is decorative but does convey the conceptual model quickly.

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, so the description must cover return values, and it does: composite positions, composite ASC/MC under conditions, internal aspects, and element synthesis. Combined with the explicit no-houses caveat, an agent has enough to call this correctly and interpret the response.

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?

With 33% schema coverage, the description should compensate more than it does. It indirectly signals that hora and local matter (they gate the composite angles), but it never clarifies the critical semantic point that sistema_casas is effectively meaningless for a midpoint composite that has no houses — an agent reading the schema will likely pass it expecting an effect.

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?

States a specific verb and resource ('Calcula o mapa composto') plus the method (midpoints) and the conceptual framing ('o mapa da relação como entidade'). It explicitly distinguishes itself from the sibling calcular_sinastria by naming it and explaining the structural difference (third chart from midpoints vs. comparing two charts).

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?

The sinastria contrast gives a clear decision rule: use composto when you want a merged relationship chart, sinastria when you want a pairwise comparison. However, it never states an explicit when-to-use or when-not-to-use condition, nor does it address the other siblings (progressões, trânsitos, revoluções).

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.