asktian

asktian_best_time_for_action

Find the most auspicious time windows in the next N days for a specific action. Use this when the user asks 'when should I do X', 'should I move this meeting', 'is tomorrow a good day to launch', 'when should I have the hard conversation', etc. Returns top 3 best windows and any windows to avoid. This is the most useful tool for real-time decision support inside any AI assistant — it lets you give specific scheduling advice instead of vague reflections.

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": {
      "birthdate": "<birthdate>"
    },
    "name": "asktian_best_time_for_action"
  }
}

Input Schema

Name	Required	Description
`action`	No	What kind of action. Pick the closest match; use 'generic' if unsure.
`birthdate`	Yes	ISO YYYY-MM-DD birthdate of the person taking the action.
`range_days`	No	How many days ahead to search. Default 7. Max 30.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 22, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions returning top 3 best windows and windows to avoid, but does not disclose side effects, authorization needs, error handling (e.g., invalid birthdate), or any limitations. Marketing language ('most useful tool') adds no behavioral value.

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 description is two sentences, with purpose stated first. The final sentence ('most useful tool...') is slightly promotional but does not detract from clarity. It could be more concise by trimming that sentence, but overall it is well-structured and front-loaded.

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?

The description explains the return format (top 3 best windows and windows to avoid) and mentions action types and range. However, it lacks details about how 'auspicious' is determined, timezone handling, or potential error cases. Given the absence of an output schema and no behavioral annotations, these gaps reduce completeness.

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% with each parameter described. The description adds value beyond the schema by advising to 'pick the closest match; use 'generic' if unsure' for the action parameter. This additional guidance merits a score above the baseline of 3.

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 states it finds auspicious time windows for a specific action, with concrete examples like asking when to do something or move a meeting. It distinguishes itself from sibling tools (e.g., asktian_today_energy) by focusing on scheduling advice rather than daily readings or compatibility.

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?

The description explicitly lists when to use the tool: 'when the user asks 'when should I do X', 'should I move this meeting', etc.' This provides clear context. It does not mention when not to use it or alternatives, but the sibling tools cover different domains, so the guidance is sufficient.

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

All asktian tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.