Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

date-anytime

Generates a random past or future date using an optional reference point, helping create test data for date-based scenarios.

Instructions

Generates a random date that can be either in the past or in the future.

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-anytime"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
Behavior2/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 discloses the randomness and that the result can fall on either side of a reference point, but says nothing about the output format, the supported range or distribution, or what happens when no reference date is given.

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?

One short sentence with no wasted words, and the key behavior is front-loaded. It is lean to the point of being slightly thin, but nothing is redundant.

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?

For a one-optional-parameter tool with no output schema, the definition covers what it produces conceptually but omits the return format and default reference behavior, which an agent would need to consume the result correctly.

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 single refDate parameter is already documented in the schema as the reference point. The description gestures at relativity ('past or future') without explicitly tying it to refDate or explaining the default when it is omitted, adding little beyond the schema.

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?

States a specific verb and resource ('Generates a random date') and adds the scope 'either in the past or in the future', which distinguishes it from sibling-style tools like date-past or date-future. It stops short of naming those alternatives explicitly, so differentiation is implied rather than reinforced.

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: an agent can infer this is the tool to pick when the direction of the date doesn't matter, but the description never states when to prefer it over a past-only or future-only variant, nor any preconditions.

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