Skip to main content
Glama

Intentions MCP Server

by io.github.intentions-me

intentions_ask_month

Read-only

Call when the user asks at month granularity or wants the best month from a multi-month window ("how is next month", "best month in 2026 to X", "下个月适合吗"). Use for trip-month selection, launch months, content-calendar planning, quarterly/annual decisions. Modes: single month, compare up to 5 months, or scan up to 12 months (returns top 5). Returns month score, element breakdown, adverse alerts. For day precision near the 4th–6th of a month use intentions_ask_day; for hour precision use intentions_ask_hour.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoDecision domain — tunes the analysis weighting. Default: general.
questionYesThe decision or action being considered
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.
monthRangeNoFind best months in range. Max 12 months. Inclusive on both ends.
targetMonthNoYYYY-MM. Default: current month
compareMonthsNoUp to 4 additional YYYY-MM months to compare against targetMonth

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark readOnlyHint=true, so the description's lack of read-only mention is acceptable. It adds helpful context on scanning limits and return elements (score, breakdown, alerts) beyond 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?

The description is well-organized: first usage, then modes, then sibling pointers. Though slightly long, every sentence adds value and is front-loaded with when to call.

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?

Given the tool's complexity (6 params, no output schema), the description covers the key aspects: modes, return values, and sibling alternatives. It omits details like 'element breakdown' but is sufficient for correct selection and invocation.

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?

The description clarifies the meaning and use of parameters beyond the schema: 'compare up to 5 months' maps to compareMonths, 'scan up to 12 months' maps to monthRange. Schema coverage is 100%, so baseline is 3, but description adds significant usage context.

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 the tool is for month-level queries, with explicit examples like 'how is next month' and 'best month in 2026'. It contrasts with sibling tools that handle day or hour precision.

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?

It provides explicit when-to-use guidance ('call when the user asks at month granularity'), explains modes (single, compare, scan), and directly names alternatives for day or hour precision.

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

All Intentions MCP Server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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.

Resources