Skip to main content
Glama

Interactive Time Lords Explorer

explore_time_lords
Read-onlyIdempotent

Generate an interactive timeline of zodiacal releasing from Spirit and Fortune, annual profections, time lords, firdaria, peaks, and loosing of the bond to identify peak periods and upcoming changes.

Instructions

Use this when the user asks for 'zodiacal releasing', 'my profection year', 'who is my time lord this year', 'my firdaria', 'loosing of the bond' or 'when are my peak periods'. Returns an interactive timeline (inline in Claude and ChatGPT; text elsewhere): releasing from Spirit and Fortune with peaks and loosing of the bond, the profection wheel, firdaria and the next changes.

CREDIT COST: 9 credits (+1 to resolve a place name; +1 for a local birth time before 1970).

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": {
      "datetime": "<datetime>"
    },
    "name": "explore_time_lords"
  }
}

Input Schema

NameRequiredDescriptionDefault
datetimeYesISO 8601; zone required (`Z`/offset, or local time plus `timezone`).
latitudeNoBirth latitude (optional with `location`).
locationNoBirth place name; coordinates win if given.
timezoneNoIANA zone for a local birth time.
longitudeNoBirth longitude (optional with `location`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.30.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description adds genuinely new behavioral facts: the render differs by client (inline in Claude/ChatGPT, text elsewhere) and the call costs 9 credits with +1 surcharges for place-name resolution and pre-1970 local birth times. It would be stronger if it noted latency or limits on the timeline range.

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?

The trigger-phrase sentence is front-loaded and followed by the return contents, with cost information isolated and clearly labeled. The quoted-phrase list is long but each entry maps to a distinct astrological technique, so little could be cut without losing routing signal.

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?

With no output schema, the description takes responsibility for describing the return (interactive vs. text timeline and its components) and it also surfaces cost, which matters for a 9-credit call. The one missing piece is any statement of how this differs from `ephemeris_time_lords`, which sits right next to it in the toolset.

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 would be 3, but the credit notes add real meaning: passing `location` triggers a geocode resolution step (+1), and a pre-1970 local birth time carries a surcharge, implicitly explaining why `timezone` matters alongside a local `datetime`. This is useful signal the schema does not convey.

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 concrete deliverable — an interactive timeline covering releasing from Spirit and Fortune, profection wheel, firdaria, and their peak/bond-loosing moments — so an agent knows exactly what comes back. It falls short of a 5 because it never distinguishes this from the sibling `ephemeris_time_lords`, which by name covers the same astrological domain.

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?

Usage is anchored in concrete user phrasings ('zodiacal releasing', 'my profection year', 'my firdaria', 'loosing of the bond', 'peak periods'), which is far better than vague context-setting. It offers no when-not guidance and does not tell the agent to prefer this over the similarly named `ephemeris_time_lords`, so routing between those two remains ambiguous.

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