Skip to main content
Glama
Céu Natal

Céu Natal

Sinastria

calcular_sinastria
Read-onlyIdempotent

Calculate synastry between two people by comparing cross-chart aspects and house overlays, then summarize harmonious, tense, and neutral contacts for relationship analysis.

Instructions

Calcula a sinastria entre duas pessoas: aspectos cruzados (planetas de A vs planetas de B), em quais casas do mapa de uma cada planeta da outra cai, e síntese com contagem de aspectos harmônicos / tensão / neutros. Útil para análise de relacionamento.

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_sinastria"
  }
}

Input Schema

NameRequiredDescriptionDefault
pessoa_aYes
pessoa_bYes
sistema_casasNoSistema de casas usado nos dois mapas. Default Placidus. Identificadores: P, K, W, E, R, C, O, B, M, T.

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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuine value beyond that by disclosing the response's internal structure (cross aspects, house placements, synthesis counts), which tells the agent what to expect back. It omits any note on behavior when birth time/place is missing, which limits house calculations.

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?

A single dense sentence front-loads the core operation and then lists outputs in a compact, scannable sequence. No filler, no repetition of the title.

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

Completeness3/5

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

For a tool with two nested person objects and no output schema, the description usefully characterizes the returned data and the synthesis counts. However, it is silent on the required inputs (both people need at least a birth date), on what degrades when hora or local is omitted, and on the house-system parameter, leaving real gaps for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% at the top level and the description says nothing about pessoa_a, pessoa_b, or sistema_casas — notably it never explains that the house-system identifiers P, K, W, E, R, C, O, B, M, T correspond to named systems, or that date/place drive the derived chart. A 2 reflects that the nested leaf properties are decently documented in-schema, but the description adds no parameter meaning of its own.

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?

The description gives a specific verb and resource ('Calcula a sinastria entre duas pessoas') and then enumerates the actual outputs: cross aspects between A's and B's planets, house overlays of one chart onto the other, and a synthesis counting harmonic/tense/neutral aspects. That level of detail makes it distinguishable from a natal or transit tool. It stops short of naming how it differs from calcular_mapa_composto, 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?

The closing phrase 'Útil para análise de relacionamento' implies the use case (relationship analysis between two people) but gives no explicit when-not guidance and names no alternatives such as calcular_mapa_composto for a composite-chart view. Usage is inferable rather than stated.

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