Skip to main content
Glama

Electional Timing

ephemeris_electional
Read-onlyIdempotent

Find favorable dates and times for launches, signings, weddings, or group events by scoring hourly windows against birth charts and filtering out void-of-course Moon periods.

Instructions

Use this when the user asks 'when should I launch / sign / marry', 'a good day next month', or wants a date good for several people ('a wedding date for both of us'). Add up to 8 people's births to score the hours against their charts too; that opens a timeline. Ask which hours of the day work if unsaid.

CREDIT COST: no people 5 / 8 / 12 for ≤30 / 60 / 120 days; with people 9 (1-2 people, ≤30 days), +1 per extra person, +3 ≤60 days, +7 ≤120. Pro; longest range Pro 30 days, Startup 60, Scale 120.

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "ephemeris_electional"
  }
}

Input Schema

NameRequiredDescriptionDefault
peopleNo
combineNo
end_dateYesISO 8601 date or zoned datetime.
latitudeNo
locationNoEvent place or lat,lon.
timezoneNo
avoid_vocNo
longitudeNo
start_dateYesISO 8601 date or zoned datetime.
lunar_phaseNowaxing, waning, new or full.
max_resultsNoDefault 5.
latest_local_hourNoWith people; default 21. 0-23 = any.
earliest_local_hourNoWith people; default 8.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.30.1
  2. Removedv4.27.0
  3. Changed1 schema field changedv4.24.2
    • changedInput schema / properties / latitude / description
      Previous value: -"Latitude of location in decimal degrees (positive = North). Resolve from a place name with location_search; never recall coordinates from memory."New value: +"Latitude of location in decimal degrees (positive = North)."
  4. Changed3 schema fields changedv4.8.0
    • changedInput schema / properties / end_date / description
      Previous value: -"ISO 8601 end date or datetime for the search window."New value: +"End of the search window. ISO 8601 date or zoned datetime; a naive clock time is rejected. Date-only resolves to 12:00 UTC."
    • changedInput schema / properties / latitude / description
      Previous value: -"Latitude of location in decimal degrees (positive = North)."New value: +"Latitude of location in decimal degrees (positive = North). Resolve from a place name with location_search; never recall coordinates from memory."
    • changedInput schema / properties / start_date / description
      Previous value: -"ISO 8601 start date or datetime for the search window (e.g., 2026-03-01)."New value: +"Start of the search window, e.g. '2026-03-01'. ISO 8601 date or zoned datetime; a naive clock time is rejected. Date-only resolves to 12:00 UTC."
  5. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so the description correctly spends its budget elsewhere: it discloses a precise credit-cost formula, per-person surcharges, and plan-capped date ranges (Pro 30 / Startup 60 / Scale 120 days). This is real added context an agent needs before calling. What it omits is any hint of the response shape — notable since there is no output schema.

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?

Two short blocks with zero filler: trigger conditions first, then a clearly labeled CREDIT COST block with a compact formula and plan limits. Every sentence carries actionable information and the front-loading is correct.

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 13-parameter tool with no output schema and mid-range schema coverage, the definition nails invocation triggers and pricing but says nothing about what comes back beyond a vague 'opens a timeline'. An agent knows when and how to call it, but not how to interpret or present results, and several secondary parameters stay opaque.

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 54%, so the description must compensate, and it only partly does: it clarifies `people` (max 8, birth data, scored against charts) and implies `earliest_local_hour`/`latest_local_hour` matter by telling the agent to ask about working hours. Unexplained are `combine` (weakened by opaque enum values weakest_link/average/balanced), `avoid_voc`, `lunar_phase`, and `max_results`, all of which exist only in bare schema fields or not at all.

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 opening clause enumerates concrete user intents ('when should I launch / sign / marry', 'a good day next month') that unambiguously identify this as a date/hour election tool, and it extends the scope to multi-person scoring. It never states the verb explicitly ('find/rank auspicious dates') and does not differentiate from the sibling electional_moment_analysis, so an agent must infer the boundary.

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?

Gives explicit trigger utterances and a scaling rule ('add up to 8 people's births… that opens a timeline'), plus a clarifying-question instruction ('Ask which hours of the day work if unsaid'). No exclusions or named alternatives (electional_moment_analysis, electional_station_tracker) are mentioned, so routing between the electional siblings is left to inference.

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