Skip to main content
Glama

dst-state

US daylight saving time state. No input: whether DST is in effect at the instant, the current New York offset, the 2026 through 2028 transition calendar, the next spring-forward or fall-back with a day and hour countdown, and the Energy Policy Act of 2005 rule, answered fresh on every call. Price: $0.005 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

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": "dst-state"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does substantial work: it discloses zero inputs, per-call freshness, and an unusual payment model ($0.005/call in USDC on Base via x402) including what happens on an unpaid call (HTTP 402 with machine-readable terms). What it omits are failure modes beyond the 402 (rate limits, upstream data source lag, whether the calendar is authoritative), which keeps it short of a 5.

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 list is front-loaded and dense with concrete deliverables, and the pricing/payment sentence is separated and purposeful. The first sentence is long and stacks five distinct return values, which is slightly hard to scan, but nothing is redundant.

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?

There is no output schema, so the description must describe the return values itself, and it does so field by field (status, offset, 2026-2028 calendar, countdown, statutory rule). Combined with the payment/authorization disclosure, an agent has everything needed to call it and interpret the response.

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?

There are zero parameters, so the baseline is 4; the description reinforces this by explicitly stating 'No input,' removing any doubt that the call takes arguments. No further parameter meaning is needed.

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 names a specific resource and scope ('US daylight saving time state') and then enumerates exactly what it yields: current DST status, the New York offset, the 2026-2028 transition calendar, the next spring-forward/fall-back with a countdown, and the EPAct 2005 rule. That enumeration clearly separates it from time-adjacent siblings such as agent-time, iso-week, and next-federal-holiday.

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?

The 'No input' phrasing and 'answered fresh on every call' imply the tool is used whenever current US DST facts are needed, which is a reasonable implied-usage signal. However, it never states when to prefer it over agent-time or next-federal-holiday, nor any exclusions or preconditions, so the guidance remains implicit rather than explicit.

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.

Resources