Skip to main content
Glama

due__cron

Deadline and date arithmetic for AI agents: business-day maths, cron to English + next runs, timezone conversion, batch date queries. GET, $0.01 per call via x402 on Base. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/due/cron

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>"
    },
    "name": "due__cron"
  }
}

Input Schema

NameRequiredDescriptionDefault
opNooperation; default 'due' = days between from and to
toNoend date (op=due)
tzNoIANA timezone e.g. Europe/London
daysNodays to add (op=add/addbiz)
fromYesstart date YYYY-MM-DD or 'today'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / days
      Added value: +{
      +  "description": "days to add (op=add/addbiz)",
      +  "type": "integer"
      +}
    • removedInput schema / properties / expr
      Removed value: -{
      -  "description": "5-field cron expression.",
      -  "type": "string"
      -}
    • addedInput schema / properties / from / description
      Added value: +"start date YYYY-MM-DD or 'today'"
    • removedInput schema / properties / n
      Removed value: -{
      -  "type": "integer"
      -}
    • addedInput schema / properties / op
      Added value: +{
      +  "description": "operation; default 'due' = days between from and to",
      +  "type": "string"
      +}
    • addedInput schema / properties / to
      Added value: +{
      +  "description": "end date (op=due)",
      +  "type": "string"
      +}
    • addedInput schema / properties / tz / description
      Added value: +"IANA timezone e.g. Europe/London"
    • changedInput schema / required
      Previous value: -[
      -  "expr"
      -]New value: +[
      +  "from"
      +]
  2. Added

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations supplied, the description does carry useful behavioral facts: it is a GET operation, costs $0.01 per call in USDC on Base (eip155:8453), and requires an x402 payment payload in params._meta. However, it says nothing about what the response looks like or how the different operations behave, which leaves a meaningful gap for a no-annotation tool.

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

Conciseness3/5

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

The feature list is front-loaded, but the pricing is stated twice in near-identical form ('$0.01 per call via x402 on Base' and 'Price: $0.01 per call in USDC on Base'), which is wasted space. The endpoint URL is useful, but the duplication and the scattershot capability list reduce efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, no-annotation, no-output-schema tool, the description covers access mechanics (HTTP, price, payment) but leaves the operational model opaque — an agent still does not know which op values exist or what a successful response contains. It is adequate but incomplete for the tool's complexity.

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%, so the schema already documents all five parameters including the op default. The description hints at operations (cron to English, next runs, business days) but never maps them to concrete op values or explains how 'from'/'to'/'days' interact with each mode, so it adds little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description lists capability areas (business-day maths, cron to English, timezone conversion, batch date queries) which conveys a date-arithmetic resource, but it reads as a marketing feature bundle rather than stating the single operation this tool performs. It also overlaps with the sibling 'due__batch' by claiming 'batch date queries', and the name 'due__cron' is only one of several advertised capabilities, so an agent cannot cleanly tell this apart from its siblings.

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 use this tool versus alternatives such as due__due, due__batch, or basedue__due, and no exclusions. The only usage-relevant content is the payment requirement, which tells the agent how to call but not when to choose it.

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