Skip to main content
Glama

AstroNest — Vedic Astrology Readings

Is this a good time? (decision timing)

resolve_timing
Read-only

Use this when the user asks whether now, or a particular date or range, is a good time for a decision such as changing jobs, marrying or investing. It takes tens of seconds. The interpret verdict for domain, voiced by a language model as an answer to a decision question, read at targetDate (or the start of dateRange, or today when neither is sent): the verdict, the running daśā and eventTiming are taken at that day. A malformed or pre-birth date is refused with 400 (invalid_target_date, invalid_date_range). Expect tens of seconds; set a client timeout of at least 90 s. Cost: 7 credits per call (only successful calls are charged; a sandbox key is free and returns a fixed sample). Voiced by a language model: allow up to 90 seconds. Example arguments: {"birthData":{"date":"1990-05-12","time":"14:35","timezone":"Asia/Kolkata","latitude":28.6139,"longitude":77.209},"domain":"career","question":"Should I accept the offer?","targetDate":"2026-11-15"}

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": {
      "birthData": "<birthData>",
      "domain": "<domain>",
      "question": "<question>"
    },
    "name": "resolve_timing"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesLife area the decision is about, e.g. career, marriage, finance or health.
questionYesThe decision question in plain language, e.g. "Is this a good time to change jobs?"
birthDataYesThe person's birth data: date, local time (omit if unknown), IANA timezone, latitude and longitude.
dateRangeNoOptional period the decision is about: start and end dates, YYYY-MM-DD. The verdict is read at `start`; `end` must not precede it.
targetDateNoOptional date the decision is about, YYYY-MM-DD. The verdict is read at this day. Takes precedence over `dateRange`.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / $defs / CorpusResolution / description
      Previous value: -"The weighed position of the classical corpus on this chart, as counts. Never source names on this surface."New value: +"How the classical evidence on this chart leans, as counts. Never source names on this surface."
  2. Changed3 schema fields changed
    • changedInput schema / properties / dateRange / description
      Previous value: -"Optional period the decision is about: start and end dates, YYYY-MM-DD."New value: +"Optional period the decision is about: start and end dates, YYYY-MM-DD. The verdict is read at `start`; `end` must not precede it."
    • changedInput schema / properties / targetDate / description
      Previous value: -"Optional date the decision is about, YYYY-MM-DD."New value: +"Optional date the decision is about, YYYY-MM-DD. The verdict is read at this day. Takes precedence over `dateRange`."
    • changedOutput schema / $defs / TimingResponse / allOf
      Previous value: -[
      -  {
      -    "$ref": "#/$defs/ForecastResponse"
      -  },
      -  {
      -    "properties": {
      -      "decisionQuestion": {
      -        "type": "string"
      -      },
      -      "exactDateAssessment": {
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "$ref": "#/$defs/ForecastResponse"
      +  },
      +  {
      +    "properties": {
      +      "decisionQuestion": {
      +        "type": "string"
      +      },
      +      "exactDateAssessment": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "referenceDate": {
      +        "description": "The day the verdict, the daśā reading and eventTiming are anchored to: `targetDate` when sent, else `dateRange.start`, else the day of the call.",
      +        "format": "date",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  }
      +]
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

It goes far beyond the annotations by disclosing critical behavioral traits: high latency ('tens of seconds,' 'set a client timeout of at least 90 s'), cost ('7 credits per call'), mechanism ('voiced by a language model'), and specific error handling for malformed dates.

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?

While detailed, the description is well-structured, front-loading the purpose and then progressing through functional and technical constraints. Every sentence carries high informational density.

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

Completeness5/5

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

Given the tool's complexity—involving temporal logic, cost, and LLM processing—the description is exceptionally complete. It covers precedence rules (targetDate vs dateRange) and operational limitations that are essential for correct invocation.

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?

With 100% schema coverage, the description successfully contextualizes the parameters within the decision-making flow (birth data, domain, question) without duplicating schema definitions. This meets the minimum viable standard for complexity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly defines the tool's purpose: judging the auspicious timing for major life decisions (e.g., marriage, career, investing). This differentiates it from raw data retrieval tools like get_ephemeris or specific readings like get_dasha.

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?

It provides clear use cases (decision types) and behavioral guidelines (latency, time constraints). It doesn't explicitly state exclusions, but the context is highly specific.

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.