Skip to main content
Glama
Sign In

GenesisCore Astrology (Western + Vedic)

by io.github.AETHER-CORE1219
OverviewDiscussionsAdmin

When Mercury, Venus or Mars changes sign (1940-2030)

get_sign_ingresses

Exact UTC times when Mercury, Venus or Mars entered each zodiac sign (Western tropical) between 1940 and 2030, filtered by a date range. Up to 60 rows.

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": {
      "planet": "<planet>"
    },
    "name": "get_sign_ingresses"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date YYYY-MM-DD (default from + 1 year)
fromNoStart date YYYY-MM-DD (default today)
planetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: results are exact UTC timestamps, restricted to the Western tropical zodiac, bounded to 1940-2030, and capped at up to 60 rows. It omits ordering and what happens when the range extends outside 1940-2030, but the row cap and boundary are the key operational facts.

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 with zero filler; the scope constraint and result cap are both packed in without repetition of the name or title.

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?

No output schema exists, so the description must convey return shape, and it does say the output is exact UTC ingress times per sign with a 60-row cap. The remaining gap is minor — sort order and out-of-range behavior — for a simple three-parameter lookup tool.

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 coverage is 67%: from/to already have descriptions, but the planet enum is undocumented in the schema. The description adds that the tool accepts Mercury, Venus or Mars and frames the 1940-2030 window that constrains the date parameters, but adds nothing about defaults or how the range interacts with the row cap.

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 states a specific verb and resource — exact UTC ingress times for Mercury, Venus or Mars entering each zodiac sign — plus the system used (Western tropical) and the date scope 1940-2030. It is clearly distinct from a retrograde-periods tool by content, though it never names a sibling to route against.

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?

Usage is implied rather than stated: the date-range filter and planet requirement signal a lookup of ingress events, but there is no explicit when-to-use, when-not-to-use, or alternative named. An agent can infer the purpose but gets no routing guidance among siblings such as get_retrograde_periods.

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

All GenesisCore Astrology (Western + Vedic) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources