Skip to main content
Glama
Sign In

HelpySelf

by com.helpyself
OverviewDiscussionsAdmin

Days Until Christmas

days_until_christmas
Read-onlyIdempotent

How many days until Christmas — counted in sleeps, not hours, and right across time zones. A HelpySelf tool (helpyself.com).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "days_until_christmas"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoThe day of the month. Defaults to the 25th. A day the month never has (30 February) is refused; 29 February counts to the next leap year. Whole calendar days are counted, the day itself is 0, and a date already passed rolls to next year.
monthNoThe month of the occasion, 1 to 12. Defaults to December. Pass month and day together to count to any yearly date, such as a birthday.
todayNoThe date to count from, as YYYY-MM-DD in the caller's own calendar. Defaults to today in UTC. The response repeats the date it counted from as countedFrom.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / day / description
      Added value: +"The day of the month. Defaults to the 25th. A day the month never has (30 February) is refused; 29 February counts to the next leap year. Whole calendar days are counted, the day itself is 0, and a date already passed rolls to next year."
    • addedInput schema / properties / month / description
      Added value: +"The month of the occasion, 1 to 12. Defaults to December. Pass month and day together to count to any yearly date, such as a birthday."
    • addedInput schema / properties / today / description
      Added value: +"The date to count from, as YYYY-MM-DD in the caller's own calendar. Defaults to today in UTC. The response repeats the date it counted from as countedFrom."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so no safety disclosure is needed. The description adds useful context about day-level counting and timezone awareness, but it does not mention default dates, rollover behavior, or return format; those details are left to the 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?

The substantive sentence is short and front-loaded with the tool's purpose and unusual unit. The trailing 'HelpySelf tool' branding is filler that does not help an agent select or invoke the tool.

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 read-only, optional-parameter tool, the combination of concise description and thoroughly documented schema is sufficient for correct invocation. Absence of an output schema is a minor gap because the description and the today parameter's note imply the response shape.

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 100% and every parameter has detailed semantics, so the description adds little beyond the schema. The timezone note weakly reinforces the 'today' parameter, but does not carry the semantic burden.

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?

The description clearly states the tool counts days until Christmas, adding unit ('sleeps') and timezone behavior. It does not explicitly distinguish it from siblings like countdown_timer or date_difference, so it misses the top score.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this over sibling tools, nor any when-not-to-use note. The phrasing implies use for a Christmas countdown, but no alternatives or exclusions are given.

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

All HelpySelf toolsInspect
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.

Resources