Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

git-commitSha

Generates a random Git commit SHA for test fixtures and mock repositories, optionally specifying the SHA length.

Instructions

Generates a random commit sha.

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

Input Schema

NameRequiredDescriptionDefault
lengthNoThe length of the commit sha.

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 reveals only that the value is random; it says nothing about the character set, whether the result is cached or unique, what the default length is when the parameter is omitted, or whether any state or permissions are involved.

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 short sentence with the key concept front-loaded and no filler. It is efficient, though the terseness leaves no room for the behavioral detail the tool otherwise lacks.

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 with one optional parameter and no output schema or annotations, so the bar is low and the description is mostly adequate. Still, for a generator the agent would benefit from knowing the output format and the default length, which the sentence omits.

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%, so the single 'length' parameter is already fully documented in the schema. The description adds no meaning beyond that and does not mention the parameter or its default at all, making baseline 3 appropriate.

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?

The description names a specific verb and resource ('Generates a random commit sha'), which clearly separates it from siblings such as git-commitMessage or git-commitDate that produce other git-related values. It is clear what the tool returns, though it doesn't state the output format (hex string) explicitly.

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, no mention of prerequisites, and no reference to alternatives or when not to use it. An agent must infer that this is a test-data generator rather than something derived from an actual repository.

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