Skip to main content
Glama
Sign In
tool-mcp-server

tool-mcp-server

by maple-awa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tool_crontab

Parse cron expressions to extract structured details and calculate future execution times. Enter an expression to get parsed fields and next scheduled runs.

Instructions

[dev] Crontab

Parameters:

  • expression (string): Expression

Outputs:

  • parsed (json): Parsed

  • nextRuns (json): Next Runs

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tool_crontab"
  }
}

Input Schema

NameRequiredDescriptionDefault
parsedNoParsed
nextRunsNoNext Runs
expressionNoExpression

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It only lists output field names and types, omitting error behavior, timezone assumptions, validation rules, or the number of next runs returned. The read-only/computational nature is implied but not disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and structured with Parameters/Outputs sections, but it is under-specified. It lacks a purpose statement and reads as a fragment rather than a coherent description. Under-specification is not good conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is inadequate. It does not describe the content or structure of parsed and nextRuns, nor any behavioral details like error handling or timezone behavior. Agents must guess what the outputs contain.

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 baseline is 3. The description adds some value by explicitly separating 'expression' as the only parameter and 'parsed'/'nextRuns' as outputs, which resolves ambiguity in the schema where all three appear as properties. However, it does not explain the expression format or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does not state what the tool does; it only presents the name 'Crontab' and lists parameters/outputs. There is no action verb like 'parse' or 'compute', so the purpose must be inferred from the output field names 'parsed' and 'nextRuns'.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool, what problems it solves, or how it relates to sibling tools. The description gives no context, alternatives, or exclusions.

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

Deploy Server

Other Tools