Skip to main content
Glama

AstroNest — Vedic Astrology Readings

Venture timing: when to commit, which business

get_venture_timing
Read-onlyIdempotent

Use this when the user asks when to start, launch, sign, borrow or expand a business, or which line of business their chart supports. A calendar of the coming months in four labels — commit (sign, open, launch), build (keep building; commit only what can be undone), guarded (low fixed cost; no lease, no borrowing) and hold (no new fixed commitments) — each window with the daśā period running and the slow transits of Saturn and Jupiter over it, and the reasons. Describe the businesses being weighed in ventures and each is ranked on how strongly the chart supports it and whether the coming periods carry it, with the grounds, its best coming period, and a caution when it needs premises during a hold; name none and the full catalogue of business types is ranked. A ranking of chart support, never a probability of success. Deterministic: no language model is called. The birth time is required. Cost: 10 credits per call (only successful calls are charged; a sandbox key is free and returns a fixed sample). Deterministic: the same input always gives the same answer. Example arguments: {"birthData":{"date":"1990-05-12","time":"14:35","timezone":"Asia/Kolkata","latitude":28.6139,"longitude":77.209},"ventures":["software and data platform for businesses","a restaurant in a leased storefront","OneDot"],"months":36}

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>"
    },
    "name": "get_venture_timing"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsNoHow far ahead the calendar runs, and the horizon each venture's period support is averaged over.
venturesNoOptional: the businesses being weighed, each described by what it does ("software for accountants", "a café with a leased storefront"). A brand name alone cannot be placed and is returned as unclassified. Omit to rank the whole catalogue.
birthDataYesThe person's birth data. The time is required: every period depends on the rising sign.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses cost (10 credits, only successful calls charged, free sandbox sample), determinism (no language model, same input yields same output), a required birth time, and the shape of the return (four labeled windows with daśā periods and Saturn/Jupiter transits, ranked ventures with grounds and best periods). It also pre-empts misuse by stating the output is a ranking of chart support, never a probability of success.

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 is front-loaded in the first sentence, followed by output shape, caveats, and cost. It is somewhat long, and the determinism claim appears twice ("no language model is called" and "same input always gives the same answer"), which is mild redundancy rather than bloat.

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?

For a nested-schema, output-schema-bearing tool, the description covers selection criteria, both operating modes, cost, determinism, the required birth time, and the interpretational caveat. An agent has enough to decide when to call it and what it will receive.

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 adds interpretive guidance about `ventures` (describe what the business does; a bare brand name is unclassified; omit to rank the catalogue) and the `months` horizon. The worked example arguments add practical value beyond the schema fields, though some guidance duplicates the schema text.

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 states a specific verb set and resource: it answers "when to start, launch, sign, borrow or expand a business" and "which line of business their chart supports." That scope is recognizably narrower than broad siblings like get_forecast or resolve_timing, so an agent can route to it without opening the schema.

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 gives an explicit trigger: "Use this when the user asks when to start, launch... or which line of business their chart supports." It also explains the two modes (named ventures vs. omitted ventures ranking the full catalogue). It does not explicitly name a sibling or a when-not condition, so it falls short of a 5.

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.