Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

git-commitEntry

Generate random Git commit log entries for test data or demos, including optional merge messages, line endings, and reference dates.

Instructions

Generates a random commit entry as printed by 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-commitEntry"
  }
}

Input Schema

NameRequiredDescriptionDefault
eolNoChoose the end of line character to use. 'LF' = '\n', 'CRLF' = '\r\n'
mergeNoSet to `true` to generate a merge message line.
refDateNoThe date to use as reference point for the commit.

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 supplied, the description carries the full burden. It does disclose the important trait that output is random/generated fake data and that the format mimics `git log`, which is genuine behavioral value, but it says nothing about determinism across calls, whether output is a string or object, or how the optional eol/merge/refDate inputs alter the result.

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 wasted words. It is efficient, though so terse that structure beyond the one clause is absent.

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?

With three optional parameters, no annotations, and no output schema, the description is thin for the complexity. It conveys the gist (a random git-log-style commit entry) but omits the return shape and the effect of each optional input, which the schema does not fully compensate for given the absence of an output schema.

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 every parameter (eol, merge, refDate) is documented in the schema, so the baseline is 3. The description adds no additional meaning about how merge affects the entry shape or how refDate anchors the generated date.

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 commit entry as printed by `git log`.' An agent can tell it produces a synthetic commit entry rather than a single field like sha or message, though it never explicitly names the sibling generators it differs from.

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 or when-not-to-use guidance and no mention of alternatives such as git-commitSha or git-commitMessage. The only signal is the tool name and the phrase 'commit entry', leaving the agent to infer that this composes the full entry rather than a component.

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