Skip to main content
Glama

Preview UTC cron schedule

bpj_preview_utc_cron
Read-onlyIdempotent

Find upcoming runs within 366 days for numeric five-field cron in UTC. Use 0 for Sunday. Supports lists, ranges and steps.

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": {
      "expression": "<expression>",
      "after": "<after>",
      "count": "<count>"
    },
    "name": "bpj_preview_utc_cron"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterYes
countYes
expressionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context the annotations do not: the output window is capped at 366 days, all evaluation is in UTC, only numeric five-field expressions are accepted, and lists/ranges/steps are supported. It stops short of saying what happens with named tokens or out-of-range values.

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?

Three short sentences, front-loaded with the core action and constraint, then syntax details. No filler and nothing repeated from the schema.

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?

For a three-required-parameter, low-complexity read tool with no output schema and full annotation coverage, this is nearly complete: the expression grammar and time horizon are documented. The remaining gap is the semantics of the 'after' anchor, which an agent must infer from 'upcoming runs'.

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 0%, so the description carries the burden and partially meets it: it explains the 'expression' format (five fields, numeric, UTC, 0=Sunday, lists/ranges/steps) and implies the window derived from 'after'. It says nothing about whether 'after' is inclusive or exclusive, or about the count range, leaving two of three parameters under-specified.

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?

States a specific verb and resource: 'Find upcoming runs ... for numeric five-field cron in UTC', with an explicit scope bound (within 366 days). An agent immediately knows this computes future cron occurrences rather than parsing, validating, or scheduling anything, and no sibling in the catalog performs this computation.

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 verb ('Find upcoming runs') and bounded by the 366-day horizon, but the description never states when to reach for this versus not, nor any prerequisite such as supplying an ISO 'after' anchor. 'Use 0 for Sunday' is a syntax rule, not usage guidance.

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.