Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

date-soon

Generates a random date in the near future, with an optional day range and reference date so you can produce future dates for testing and data seeding.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
daysNoThe range of days 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

C2.9/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 burden. It does disclose that the result is random, but it omits key behavior: what the default range is when the optional days parameter is omitted, what reference date is assumed (today?), and what format the returned date takes.

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. It is efficient, though its brevity edges toward under-specification rather than tight completeness.

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

Completeness2/5

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

For a generator with zero annotations, zero required parameters, and no output schema, the description should state defaults and return format. It does neither, so an agent cannot know what it gets when calling with no arguments.

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%, and both parameters (days, refDate) are documented in the schema, so the baseline is 3. The description adds no meaning beyond it, though 'near future' weakly hints that days defaults to a small value.

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?

"Generates a random date" is a specific verb+resource, and "in the near future" conveys scope. However, it never distinguishes itself from the closely named siblings date-future, date-recent, and date-anytime, so an agent cannot tell from the text alone which one to pick.

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 guidance and no mention of alternatives. With siblings like date-future and date-recent present, the absence of any routing hint (for example, 'use date-future for a bounded future date') leaves selection to guesswork.

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