Skip to main content
Glama

next_deadlines

Read-only

Time-aware "what statutory filing is due next?" Returns upcoming filings sorted soonest-first, each with a computed nextDue date and daysUntil. Optional country, withinDays (e.g. the next 30/60/90 days), limit, and asOf (reference date, defaults to today UTC). A concrete date is computed only when it can be placed unambiguously (monthly filings with a due day, or entries with explicit annual dates); quarterly/half-yearly entries given only a day-of-month and per-event filings come back with scheduleVaries: true and nextDue: null. Dates rotate annually — confirm against each source URL.

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

Input Schema

NameRequiredDescriptionDefault
asOfNoReference date (YYYY-MM-DD) to compute "next" from. Defaults to today (UTC).
limitNoMax rows to return (default 25).
countryNoRestrict to one country (ISO-2). Omit for every country.
withinDaysNoOnly return filings whose next due date falls within this many days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description goes well beyond them by disclosing that nextDue is null and scheduleVaries=true for quarterly/half-yearly and per-event entries, that a date is computed only when unambiguous, that dates rotate annually, and that the caller should confirm against the source URL. These are real behavioral limits an agent cannot get from the schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead question establishes purpose immediately, followed by the sorted output, then parameters, then the caveat about null dates and staleness. Every clause carries information (field names, defaults, ambiguity rule, source caveat) with no filler.

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?

With no output schema, the description carries the burden of explaining return values and does so: nextDue, daysUntil, scheduleVaries, and source are all named, along with the null case. For a read-only, zero-required-parameter query tool this is complete enough to invoke correctly.

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%, so all four parameters (asOf, limit, country, withinDays) are already documented with defaults and bounds. The description only reinforces them with the 30/60/90-day example, adding marginal meaning beyond the structured data — baseline 3 is the right level.

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?

Opens with a concrete resource and framing ("what statutory filing is due next?") and states the output shape (sorted soonest-first with nextDue and daysUntil), which is far more specific than a restated title. It does not, however, name or contrast against the obvious sibling compliance_deadlines, so the agent must infer the division of labor from the ordering/computation language alone.

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?

Usage is implied by the question framing and by the withinDays example ("the next 30/60/90 days"), which tells an agent the intended query pattern. There is no explicit when-not guidance and no mention of compliance_deadlines as the alternative for a full schedule listing, leaving the routing decision to inference.

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