Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

system-cron

Generate random cron expressions for testing and mock scheduling data, optionally including a year or labels such as @daily and @monthly.

Instructions

Returns a random cron expression.

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": "system-cron"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeYearNoWhether to include a year in the generated expression.
includeNonStandardNoWhether to include a '@yearly', '@monthly', '@daily', etc text labels in the generated expression.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full burden. It does disclose the key behavioral trait, non-determinism ('random'), but says nothing about whether the returned expression is guaranteed to be syntactically valid or about reproducibility and seeding. For a simple value generator this is adequate but thin.

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 front-loaded sentence with no filler or restated title. It is efficiently sized for the tool's simplicity, though the spare length leaves room unused for behavioral or output detail.

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

Completeness3/5

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

The tool is simple, has no required parameters, no nested objects and no output schema, so the description needn't explain return structure in depth. Still, it omits what the returned value looks like (a plain string, a five- or six-field expression) and whether the random generation is drawn from a curated set; those gaps matter slightly for an agent deciding whether to call it.

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%: both includeYear and includeNonStandard carry their own descriptions, so the baseline is 3. The description adds no further meaning about how these flags affect the output, such as which fields gain a year component or how @daily-style labels interact with field count.

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 and resource: it returns a randomly generated cron expression. An agent can immediately tell this is a synthetic-data generator, distinct from the file/animal/airline value generators in the sibling list. It stops short of stating scope (e.g., which cron fields vary), but the purpose is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives or prerequisites. The agent must infer from the tool name alone that this is for producing mock cron strings, e.g., for test fixtures.

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