Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

git-commitMessage

Generates a random Git commit message for prototypes, demos, or test repositories that need varied, plausible commit text.

Instructions

Generates a random commit message.

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-commitMessage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden, and it does disclose the essential trait: output is randomly generated (non-deterministic, same call yields different results) and requires no input. It does not say what shape the message takes (subject line only vs. subject plus body, conventional-commit style, length) or that the result is fake data unsuited for real commits.

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 or redundancy. Nothing is wasted and the reader knows the purpose immediately.

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?

There is no output schema and no annotations, so the description is the only source of return-value information, and it only implies a string message without specifying format or determinism guarantees. For a trivial zero-parameter generator this is close to adequate but leaves a real gap about what comes back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is empty, so there is no parameter meaning the description needs to convey. Baseline 4 applies; no confusion is possible about inputs.

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 commit message" names a specific verb (generates) and resource (commit message) and adds the key qualifier "random." It does not distinguish itself from sibling generators such as git-commitEntry or git-commitSha, but the resource named is distinct enough for an agent to identify it.

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 statement of when to use this tool versus the adjacent git-commitEntry, git-commitSha, or git-commitDate generators, and no note that it is for synthetic/placeholder data rather than real repository history. The agent must infer all routing from the name alone.

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