Skip to main content
Glama

cron_next

Paid $0.02 (x402, USDC Base): cron solver - next N execution times (UTC) for a standard 5-field cron expression. Args: expr (string), n (int, default 5).

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": {
      "expr": "<expr>"
    },
    "name": "cron_next"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNo
exprYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does disclose the notable paid behavior: "$0.02 (x402, USDC Base)" and UTC output. However, it does not clarify invalid-expression handling, n limits, exact return shape, or whether there are any rate/payment failure behaviors.

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 definition is compact and front-loads the paid nature and tool purpose before listing arguments. Every element earns its place, and there is no filler or redundant exposition.

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 simple calculator, the description covers purpose, payment cost, parameters, default n, and output timezone. Still, with no annotations, no output schema, and 0% schema description coverage, it leaves gaps around invalid cron handling, n constraints, and exact return format.

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?

Schema description coverage is 0%, but the description adds meaningful parameter context beyond the schema: expr is a standard 5-field cron expression, and n defaults to 5. It does not document n bounds or explicitly mark expr as required, but it is sufficient for a simple two-parameter tool.

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 states a specific resource and result: "cron solver - next N execution times (UTC) for a standard 5-field cron expression." This clearly distinguishes it from time/epoch/color/random utility siblings by naming cron expressions and execution times as the domain.

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 "cron solver" and the paid-cost note gives a practical condition, but there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. An agent can infer context but gets no routing help beyond the purpose itself.

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