Lordevo Shop (x402 website checks)

Cron next run times + plain-English description ($0.002/call)

cron_next

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Data utilities] Reads a 5-field cron expression (or @daily-style macro) and returns the next N run times in UTC and in the given time zone, a plain-English description and the expanded fields. Input: cron, optional tz (default UTC), count 1-20, after. Limits: no seconds field, no L/W/#. Offline.

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

Input Schema

Name	Required	Description	Default
`tz`	No	IANA time zone the schedule runs in (default UTC)
`cron`	Yes	5-field cron expression (minute hour day-of-month month day-of-week), or @hourly, @daily, @weekly, @monthly, @yearly
`after`	No	Start after this time (ISO 8601 or Unix seconds; default now)
`count`	No	How many next runs, 1-20 (default 5)	5
`trial`	No	Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms.

Output Schema

Name	Required	Description
`tool`	No
`cache`	No
`count`	No
`notes`	No
`_trial`	No	Present when the call was a free trial call.
`provider`	No
`timezone`	No
`next_runs`	No
`price_usd`	No
`expression`	No
`normalized`	No
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / trial / description

Previous value: -"Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms."New value: +"Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms."

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / trial

Added value: +{
+  "description": "Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms.",
+  "type": "boolean"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "required": [
+        "tool",
+        "description",
+        "next_runs"
+      ]
+    },
+    {
+      "properties": {
+        "accepts": {
+          "type": "array"
+        },
+        "error": {
+          "type": "string"
+        },
+        "resource": {
+          "type": "object"
+        },
+        "x402Version": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "x402Version",
+        "accepts"
+      ]
+    },
+    {
+      "properties": {
+        "charged": {
+          "type": "boolean"
+        },
+        "error": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "_trial": {
+      "description": "Present when the call was a free trial call.",
+      "type": "object"
+    },
+    "cache": {
+      "type": "object"
+    },
+    "count": {
+      "type": "integer"
+    },
+    "description": {
+      "type": "string"
+    },
+    "expression": {
+      "type": "string"
+    },
+    "next_runs": {
+      "items": {
+        "properties": {
+          "local": {
+            "type": "string"
+          },
+          "utc": {
+            "type": "string"
+          },
+          "weekday": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "normalized": {
+      "type": "string"
+    },
+    "notes": {
+      "type": "array"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "timezone": {
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedNov 1, 2026

TDQS

A3.7/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 safety is covered. The description adds genuinely new behavior: per-call price, the trial quota (3 per IP per UTC day), the fact that it runs offline, and the accepted grammar. It does not say what error is returned for an invalid expression, which keeps it below a 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?

Two sentences, both dense with facts and no filler. The trade-off is that the pricing sentence leads, pushing the actual purpose into second position, and the second sentence is a long run-on packing return shape, inputs and limits together.

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?

An output schema exists, so the description is not obligated to explain return values, yet it still names them (run times, plain-English description, expanded fields). Cost, trial quota, default tz, count range, start anchor and grammar limits are all present. Only error behavior for malformed cron input is missing.

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 every parameter with defaults and formats, making 3 the baseline. The description restates cron/tz/count/after without adding syntax the schema lacks, and its only real addition, the 'no seconds field, no L/W/#' restriction, is a grammar constraint rather than per-parameter meaning.

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?

States a specific verb and resource: 'Reads a 5-field cron expression (or @daily-style macro) and returns the next N run times in UTC and in the given time zone, a plain-English description and the expanded fields.' That is unmistakable and would not be confused with date_calc or time_convert. It stops short of naming those siblings explicitly, so it loses the top mark.

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 input shape (use this when you have a cron expression), and it points to the try_free sibling for the free path. It never states when NOT to use it versus date_calc/time_convert for general date arithmetic. The syntax limits ('no seconds field, no L/W/#') function as a partial exclusion list, which is better than nothing but not full routing guidance.

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

All Lordevo Shop (x402 website checks) tools Inspect

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

Need Help?