Skip to main content
Glama

NatalChart.AI Astrology

Best days for an activity

best_days
Read-onlyIdempotent

Every day of a window of up to 62 days scored for one activity (general, business, romance, health, creative, travel, home, clarity): helping and hindering transits, Moon phase and sign, void of course. The five best days first. (Premium or MAX) Use it to pick dates for an activity within the next weeks.

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": {
      "birth": "<birth>"
    },
    "name": "best_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoAt most 62 days after from; 30 days by default.
fromNo
birthYes
activityNo
timezoneNoIANA zone that sets where each day begins. UTC by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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-open-world, so the description focuses on what the annotations can't say: which astrological factors drive the score, that results are ranked with the top five first, the 62-day cap, and the premium tier requirement. It doesn't describe the score scale or the shape of a returned day entry, which matters given 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with what is computed and ordered before the usage line. The inline parenthetical enum list is slightly heavy but earns its place because the enum has no per-value descriptions in the schema.

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?

For a five-parameter, nested-input tool with no output schema, the description covers the computation, ordering, window cap, and access tier, while the nested birth object is well documented in the schema itself. The remaining gap is the return value detail (score range/format per day), which an agent would otherwise have to discover empirically.

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 description coverage is only 40%, so the description has to compensate. It does explain the activity dimension well by enumerating all eight values and tying them to 'one activity,' and it restates the 62-day window limit. But it adds nothing about 'from'/'to' defaults, the day-boundary meaning of the top-level 'timezone,' or the nested birth object, leaving those to the schema.

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?

States a specific resource and computation: every day in a window of up to 62 days scored for one named activity, with the factors used (transits, Moon phase/sign, void of course) and the output ordering (five best days first). That is enough to distinguish it from sibling tools like daily_transits or best_cities without opening a schema, though no sibling is named explicitly.

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 a clear selection context: 'Use it to pick dates for an activity within the next weeks,' which cleanly separates date-picking from the location-oriented siblings. It also discloses the '(Premium or MAX)' access prerequisite. It stops short of naming when to prefer daily_transits or location_score instead, so no exclusions are offered.

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.

Resources