Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

system-semver

Returns a semantic version string for generating realistic version data in tests, fixtures, or mock API responses.

Instructions

Returns a semantic version.

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": "system-semver"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the entire behavioral burden and discloses almost nothing: not whether the value is random per call, not whether pre-release/build metadata can appear, not whether output is deterministic. The only behavior revealed is the return type, which is largely a restatement of the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler, so nothing is wasted, but the sentence is nearly identical to the tool name and adds no distinguishing information. Brevity here reflects under-specification rather than disciplined structure.

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?

For a zero-parameter generator with no annotations and no output schema, the description is the only place an agent can learn the output contract. It omits the format guarantees (MAJOR.MINOR.PATCH, optional prerelease/build segments) that matter most for a semver generator.

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, so there is no parameter semantics to convey; the empty schema with additionalProperties:false is self-consistent and the baseline of 4 applies.

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

Purpose3/5

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

"Returns a semantic version" states a resource (a semantic version string) but the verb is generic and the description never confirms this is a value generator rather than a parser/validator. An agent reading only this line could plausibly assume it parses a version rather than producing a random one, though the sibling naming pattern (system-fileName, system-mimeType) hints at same shape of generator.

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?

No when-to-use guidance, no exclusions, and no mention of alternatives. Since the siblings are all faker-style value generators, the agent must infer from the namespace alone that this is the semver-flavored member of that family.

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