Skip to main content
Glama

dev_tools_cron_explain

[$x402 pago por llamada] Explica en lenguaje natural una expresión cron de 5 campos.

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": "dev_tools_cron_explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
exprYesExpresión cron de 5 campos: minuto hora dia-del-mes mes dia-de-semana.
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the key trait: this is a paid x402 call ("pago por llamada"), reinforced by the schema note that omitting x_payment yields a 402. However, it says nothing about output language/format, latency, or idempotency, so the disclosure is partial for an annotation-free tool.

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?

A single functional sentence with the payment marker front-loaded; every element earns its place. The bracketed "[$x402 pago por llamada]" prefix is useful but slightly cryptic in isolation.

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 simple two-parameter, read-only string-transform tool with a fully specified schema and no output schema, the description plus schema covers what an agent needs to invoke it. Only the expected shape of the natural-language explanation (language, length, edge-case handling) is left unstated.

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%, with both `expr` (5-field format) and `x_payment` (x402 header, 402 fallback) fully documented in the schema itself. The description adds no parameter-level detail beyond restating the 5-field constraint, so the baseline of 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?

The description names a specific verb ("Explica en lenguaje natural") and resource ("una expresión cron de 5 campos"), so an agent immediately knows exactly what it produces. No sibling can be confused with it, since none of the other dev_tools deal with cron syntax, though the description never explicitly draws that distinction.

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 only implied: the tool is for understanding a cron expression, and the 5-field restriction hints at scope. There is no statement of when to use it versus alternatives, no prerequisites, and no note about behavior for invalid or 6-field expressions.

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