Tinplate Edge AI Safety, Security & EU Compliance

tinplate_cron_explainer

Read-onlyIdempotent

Cron & Schedule Explainer & Validator API: Validate cron expressions, translate to plain English, and compute next N runs with DST. (Endpoint: POST /v1/cron-explainer)

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>",
      "timezone": "<timezone>"
    },
    "name": "tinplate_cron_explainer"
  }
}

Input Schema

Name	Required	Description
`timezone`	Yes	Parameter 'timezone' (e.g. "Europe/Budapest")
`next_runs`	No	Numeric parameter 'next_runs' (e.g. 3)
`expression`	Yes	Parameter 'expression' (e.g. "0 9 * * 1-5")
`reference_time`	No	Parameter 'reference_time' (e.g. "2026-11-14T08:00:00Z")

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful behavior beyond that by disclosing DST handling for next-run computation and the POST endpoint, though it does not mention limits on next_runs or validation error behavior.

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?

The definition is a single front-loaded sentence plus endpoint information, with no wasted prose. The only slight redundancy is repeating the tool-title phrasing at the start.

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 four-parameter, read-only tool with annotations covering safety and schema coverage covering parameters, the description gives enough operational context to invoke it correctly. It does not explain return values, but no output schema exists and the schema carries the parameter detail.

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 100%, so the schema already documents all four parameters and their examples. The description references next N runs and DST handling but does not add syntax, constraints, or meaning beyond the schema baseline.

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 names a specific resource and three concrete operations: validate cron expressions, translate to plain English, and compute next N runs with DST. An agent can identify exactly what the tool does without opening the schema.

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?

The description implies usage for cron and schedule work through its operation list, but it does not state when to use this tool versus alternatives or any exclusions. Usage is inferable but not explicitly guided.

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

All Tinplate Edge AI Safety, Security & EU Compliance 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?