Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

git-commitDate

Generate a Git-compatible commit date string formatted like git log, using an optional reference date to produce consistent commit timestamps for fake data.

Instructions

Generates a date string for a git commit using the same format as git log.

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": "git-commitDate"
  }
}

Input Schema

NameRequiredDescriptionDefault
refDateNoThe date to use as reference point for the commit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral disclosure burden, but it only states that the output is a git log-formatted date string. It does not explain default behavior when refDate is omitted, timezone handling, determinism, or the exact format.

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?

The description is a single clear sentence with the purpose and format front-loaded. It contains no unnecessary wording or repetition.

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?

The tool is simple, but it has no output schema or annotations, so the description must carry more weight. It states the output format broadly but omits exact formatting details and default behavior when refDate is absent.

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 the single optional `refDate` parameter is documented in the schema. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: "Generates a date string for a git commit" and specifies the output format as matching `git log`. This clearly distinguishes it from sibling tools like git-commitMessage, git-commitSha, and generic date tools.

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?

The phrase "for a git commit" implies the context in which this tool is used, but there is no explicit guidance on when to choose it over date-anytime or other git-commit-related siblings. No exclusions or alternatives are mentioned.

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