Skip to main content
Glama
Sign In

Clawhard Studio

by com.clawhard
OverviewDiscussionsAdmin

Would this cron fire at a datetime?

tick_matches
Read-onlyIdempotent

Use when you need a yes/no on whether a cron expression would fire at a specific instant in a timezone — for example before shipping a schedule that crosses a DST transition, or to verify a single expected fire. Example: {"expression":"0 9 * * 1-5","timezone":"America/New_York","at":"2026-11-06T14:00:00Z"}. Returns fires true/false, the local wall time of that instant, and DST notes if the local time is in a gap or fold.

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>",
      "at": "<at>"
    },
    "name": "tick_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
atYesISO datetime to test, e.g. 2026-11-06T14:00:00Z.
timezoneNoIANA timezone. Default UTC.
expressionYesCron expression (5 or 6 fields, or a nickname like @hourly).

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, closed-world. The description goes beyond that by disclosing the return payload — boolean fires, the local wall time, and DST gap/fold notes — which is meaningful since no output schema exists. It says nothing about invalid-expression error behavior, so it stops short of 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?

Front-loaded with 'Use when...', then a concrete example, then the return shape — a tight three-move structure with no filler. The example datetime repeats the schema's own example string, a minor redundancy, but the full call with all three parameters still earns its place.

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?

For a three-parameter, read-only predicate tool with no output schema, the description covers purpose, triggering scenarios, a full example call, and the return values including DST edge-case output. An agent has everything needed to select and invoke it 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 coverage is 100%, so the schema already documents expression, at, and timezone including formats and defaults. The worked example adds a composite call pattern but no syntax or constraint detail beyond what the schema already states. Baseline 3 applies.

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?

Names a specific verb and resource: a yes/no check of whether a cron expression fires at a specific instant in a timezone. It is clearly distinguishable in intent from a next-runs lister, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete when-to-use scenarios: validating a schedule that crosses a DST transition before shipping it, or confirming a single expected fire. It implies the single-instant use case vs listing upcoming runs, but does not state an explicit exclusion or name the sibling tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Clawhard Studio toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources