Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Week number and date facts: ISO week, weekday, day of year, quarter

date_info
Read-only

Weekday, ISO week number and week-year, day of the year, quarter, days in the month, leap year, Unix timestamp and whether it is a weekend, for any date. Use for calendar and reporting logic. Example: date=2026-10-18. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": "date_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate or ISO timestamp (default today)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, and the description reinforces this with 'reads or computes only and changes nothing.' It adds genuinely non-obvious behavior beyond the annotations: per-call pricing, a free tier, failed calls free, and that repeated calls are charged (which explains idempotentHint=false from a billing perspective). It omits timezone handling and invalid-input behavior.

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 output facts are front-loaded in one dense clause, followed by usage, example, and billing. It is efficient, though the pricing/credits sentence is long and slightly displaces the calendar-facts message.

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?

With no output schema, the description carries the return-value burden and does so by enumerating every field returned, plus cost and side-effect status for a one-optional-parameter tool. Gaps are minor: no mention of date validation errors or timezone assumptions.

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 coverage is 100% for the single 'date' parameter ('Date or ISO timestamp (default today)'), so the baseline is 3. The description adds only a concrete example (date=2026-10-18), which shows format but contributes little meaning beyond 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?

The description enumerates the exact facts returned — weekday, ISO week number and week-year, day of year, quarter, days in month, leap year, Unix timestamp, weekend flag — for any date, which is far more specific than the title alone. It does not explicitly differentiate itself from siblings like unix, date_business_days, or calc_age whose outputs partially overlap, so it stops short of a 5.

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

Usage Guidelines3/5

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

'Use for calendar and reporting logic' implies a context but gives no when-not conditions and names no alternative tool for overlapping needs (e.g. Unix conversion or business-day math). The billing note ('first 25 free', 'failed calls free') does add practical decision-relevant context, keeping it above a 2.

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.