Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

date-recent

Generates a random date in the recent past, letting you set a day range and reference date for test data or date inputs.

Instructions

Generates a random date in the recent past.

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": "date-recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoThe range of days the date may be in the past.
refDateNoThe date to use as reference point for the newly generated date.

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 carries the full behavioral burden. It does disclose the essential trait that the output is random rather than derived, which is valuable. But it omits default behavior when days or refDate are omitted, the distribution of randomness, and the return format, which an unannotated tool should cover.

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 short sentence with zero wasted words, and the key concept (random date, past scope) is front-loaded. Its brevity is efficient, though it borders on under-specification for the tool's branching behavior.

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 with two optional parameters and no output schema, so the bar is low. Still, the description never states what a returned date looks like or what the defaults are, leaving gaps an agent would want filled before calling 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%, so both parameters are already documented in the schema. The description adds only the framing 'recent past,' which loosely corresponds to days but does not explain defaults or the interaction between days and refDate. Baseline 3 is appropriate.

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 gives a specific verb and resource: generate a random date, scoped to the recent past. An agent can tell this is a date-generation utility. However, it never distinguishes itself from sibling generators such as date-past, date-soon, or date-between, so the exact boundary of 'recent past' is left unclear.

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?

No guidance is given on when to choose this over date-past, date-between, or date-future. There is no mention of how 'recent' is defined or what happens when the caller needs a wider or narrower window, so an agent must guess.

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