Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

vehicle-vrm

Generates a vehicle registration number (VRM) to populate fake records, test datasets, and placeholder vehicle data.

Instructions

Returns a vehicle registration number (Vehicle Registration Mark - VRM).

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": "vehicle-vrm"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden and says nothing about determinism, whether each call produces a new random value, expected format/locale (the term VRM is UK-flavored but not stated), or error behavior. It confirms a value comes back but discloses no behavioral traits beyond that.

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 padding; the acronym expansion is the only slight redundancy but it is genuinely clarifying. It is efficient, though it leaves room for a short clause on output format.

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 (no params, no nested objects, no output schema), so the description is nearly adequate. The remaining gap is what the returned value looks like — assumed random generation and a specific national format are not stated, which matters for a data-fabrication tool.

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 schema has zero parameters, so there is no parameter meaning to add; the baseline of 4 applies. Nothing in the description misrepresents the call signature.

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 gives a concrete verb and resource ("Returns a vehicle registration number") and expands the acronym VRM, which distinguishes it from siblings such as vehicle-vin and vehicle-color. It does not, however, state that it generates synthetic/mock data, which is the shared behavior of the surrounding vehicle-* family.

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 mention of when to pick vehicle-vin vs vehicle-vrm, and no locale or context restrictions. The only signal is the noun itself, leaving the agent to infer the use case.

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