Skip to main content
Glama

Progressions and solar arc, now

progressions
Read-onlyIdempotent

The progressed chart as of today: secondary progressions (a day after birth for each year of life) or solar arc directions (every point moved by the Sun's progressed arc).

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": {
      "date": "<date>",
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "timezone": "<timezone>"
    },
    "name": "progressions"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD
timeNoLocal clock time, HH:MM (24-hour). If unknown, omit: noon is used, and houses and angles are then unreliable.
placeNoBirthplace name, echoed back so the user can check the coordinates
methodNoDefault secondary
latitudeYesBirthplace latitude in decimal degrees (north positive)
timezoneYesIANA time zone of the birthplace, e.g. America/New_York. Historical daylight saving is applied from it.
longitudeYesBirthplace longitude in decimal degrees (east positive)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description's useful addition is the temporal framing ('as of today' – birth data in, chart for the current date out), but it says nothing about what the response contains (planets only vs. houses/angles) or how unreliable results are when time is omitted.

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 sentence with the resource front-loaded and each clause earning its place by defining the two modes. No filler or repetition of schema fields.

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?

With 7 parameters, no output schema, and no annotations covering output shape, the description should say what the returned progressed chart includes and note the degraded-accuracy case when 'time' is omitted. It covers the temporal semantics but leaves output content entirely to inference.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds meaning the schema lacks: it defines what 'secondary' (a day after birth per year of life) and 'solar_arc' (all points moved by the Sun's progressed arc) actually compute, whereas the schema only says 'Default secondary'.

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 names a specific astrological resource (the progressed chart as of today) and enumerates its two computation modes, so the agent knows exactly what is computed. It does not differentiate from siblings such as transits or natal_chart, which is the classic adjacent concept an agent could confuse it with.

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 parentheticals explain what secondary progressions and solar arc directions mean, which implicitly helps the agent pick a method, but there is no explicit when-to-use guidance, no statement of when to prefer transits or returns instead, and no note that 'method' defaults to secondary (that is only in the schema).

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.

Resources