Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

date-past

Generates a random date in the past, using an optional reference date and year range to produce test data for apps, fixtures, and schedules.

Instructions

Generates a random date in the 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-past"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNoThe range of years 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.3/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 essential trait: output is randomly generated, not deterministic. However, it omits what defaults apply when years or refDate are omitted (is refDate the current date?), how far back a random year may land, and what format the date is returned in, which matters if the agent needs to chain the result.

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

Conciseness5/5

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

A single front-loaded sentence with zero filler; the core behavior is stated immediately and nothing is extraneous for the amount of information conveyed.

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?

No annotations and no output schema exist, so the description must carry behavioral context, and it covers only the randomness. Default behavior for the two optional parameters and the return format are left unspecified, a noticeable gap for a generator whose output an agent must consume.

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 (years, refDate) are already documented in the schema, and the description adds no meaning beyond that. Baseline of 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource ("Generates a random date") plus a scope qualifier ("in the past"), so an agent can immediately tell it apart from a future-date or between-dates tool. The sibling names date-future and date-anytime imply natural contrasts, but the description does not name them explicitly, so the differentiation stops short of full clarity.

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 explicit when-to-use or when-not-to-use guidance. "In the past" hints at the alternative of a future-date tool, but no sibling is named and no precondition is stated to guide the agent toward this tool over date-anytime or date-between.

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