Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

date-between

Generate a random date between specified early and late boundaries for testing, simulations, or mock data.

Instructions

Generates a random date between the given boundaries.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "date-between"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe late date boundary.
fromYesThe early date boundary.

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 does disclose the key trait of non-determinism ("random"), which is genuinely useful, but says nothing about whether boundaries are inclusive or exclusive, what happens if from is later than to, or what type/format the returned value takes.

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 no filler; the operation, the randomness, and the constraint all appear immediately.

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?

With no annotations and no output schema, the description should explain what the tool returns, but it doesn't state the return type or format. Boundary semantics and error conditions for an inverted range are also unaddressed, leaving real gaps for a two-required-parameter tool.

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%, and the schema already labels to as "the late date boundary" and from as "the early date boundary." The description adds only the framing of "boundaries" and no format details, so it neither compensates for nor adds to what the schema provides.

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") plus the scoping constraint ("between the given boundaries"), which is enough for an agent to understand the operation. It does not, however, distinguish itself from plausible siblings such as date-betweens or date-anytime, so the agent must guess which date-range tool applies.

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 context is only implied: an agent can infer it should call this when it needs a random date inside a range. There is no explicit when-to-use or when-not-to-use guidance and no mention of the neighboring date tools that could serve similar purposes.

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