Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

date-future

Generates a random date after the reference date, optionally within a set number of years ahead, for test data and scheduling scenarios.

Instructions

Generates a random date 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-future"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNoThe range of years the date may be in the future.
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?

With no annotations, the description still discloses the key behavioral trait that the output is randomly generated and bounded to a future window. It omits other relevant traits: whether the reference point defaults to now, whether results are deterministic, and what textual format the date takes on return.

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 the core scope front-loaded and no filler. It is efficient, though the extreme brevity means little is structured beyond the one clause.

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?

This is a simple two-parameter, zero-required generator with no output schema, so heavy documentation is not required. However, because no output schema exists, the description should state the shape of the returned date, and it does not.

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. The description adds no further meaning about how years bounds the range or how refDate interacts with the future constraint, so the baseline of 3 applies.

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 ("Generates a random date") and constrains it with "in the future," which implicitly separates it from date-past and date-anytime. It stops short of naming a sibling or stating explicit boundaries, so the agent must infer the distinction from the scope phrase alone.

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 and no named alternative such as date-past, date-between, or date-soon. The "in the future" phrase hints at a use case but leaves the choice between similar date tools to inference.

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