Skip to main content
Glama

intentions_ask_hour

Read-only

Call when the user asks about timing within a specific day — best hour to act, morning vs afternoon, when during the day ("best time today to X", "morning or afternoon for Y", "几点去见面好"). Use for interview slots, meeting times, send/publish times, departure times, workout windows. Pro subscription required; on the free tier this returns a subscription_required error whose payload suggests intentions_ask_day for day-level analysis or intentions_energy_chart with period weekly / yearly for a visual overview (the caller LLM decides whether to retry). Modes: single (date+hour), compare up to 5 hour-pairs, or scan all 12 two-hour blocks of one day. Accepts any clock hour 0..23; internally mapped to the containing 2-hour block midpoint (0/2/4/…/22). 23:00–23:59 automatically rolls the effective day forward by one. Every output entry includes a window { start, end } local wall-clock span (YYYY-MM-DDTHH:MM, no timezone offset — interpret in the same frame as the input hour). Always cite this when presenting the time. Returns score, verdict, adverse alerts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoDecision domain — tunes the analysis weighting. Default: general.
questionYesThe decision or action being considered
bestInDayNoFind best hours within a single day. Each entry carries an explicit `window` span.
birthInfoNoOptional override. If provided, all 6 fields required: { year, month, day, hour, minute, gender } — use null for unknown hour/minute/gender. Omit entirely to use the stored profile.
targetDateNoYYYY-MM-DD. Default: today (single mode only)
targetHourNoClock hour 0..23. Auto-rounded to the containing 2-hour block. 23:XX rolls the effective day forward by one.
compareHoursNoUp to 4 additional (date, clock-hour 0..23) pairs to compare against targetDate+targetHour. Pairs that resolve to the same 2-hour block (e.g. hours 7 and 8 on the same date) are deduplicated — submit distinct blocks if you want distinct results.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true; description adds extensive behavioral context: pro subscription required, free tier error handling, three modes (single, compare, scan), internal mapping to 2-hour blocks, 23:00-23:59 rolls day forward, output includes window span with no timezone offset. No contradiction with annotations.

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?

Description is concise considering the complexity; front-loaded with purpose and usage. Every sentence adds value, but could be slightly better structured (e.g., separate sections for modes, edge cases, output). Still effective and efficient.

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 (7 params, nested objects, no output schema), description covers usage context, subscription behavior, all three modes, edge cases (hour roll), and output format (window, score, verdict, alerts). No output schema but description sufficiently informs agent of return structure.

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%, baseline 3. Description adds meaningful details beyond schema: explains targetHour auto-rounding, compareHours deduplication rule, bestInDay.top default, and output window format. Only minor gap: no default for category or targetDate described beyond schema.

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?

Description clearly states the tool is for timing within a specific day (best hour, morning vs afternoon). Uses specific verbs like 'Call when the user asks about timing within a specific day' and distinguishes from siblings by naming alternatives (intentions_ask_day, intentions_energy_chart).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (user asks about timing within a day), mentions pro subscription requirement and free tier behavior with clear fallback suggestions. Provides alternatives for different granularity (day-level analysis, visual overview).

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.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool targets a distinct time granularity (hour, day, month, year) or a specific function (chart, profile management). No two tools overlap in purpose; the descriptions clearly differentiate them.

Naming Consistency5/5

All tools follow a consistent 'intentions_<verb>_<noun>' pattern. The verb for time queries is uniformly 'ask', and profile tools use 'get'/'set'. The 'energy_chart' tool is the only slight deviation but still readable and fits the pattern.

Tool Count5/5

Seven tools is an ideal size for this domain. Each tool serves a well-defined purpose without unnecessary redundancy or gaps, covering time queries at multiple granularities, visual charts, and profile management.

Completeness5/5

The tool surface fully covers the intended functionality: asking about timing at hour, day, month, and year levels; generating visual charts; and managing user profile. No obvious dead-ends or missing operations for the stated purpose.