Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

vehicle-color

Returns a random vehicle color to help generate fake automotive data for tests, demos, or sample records.

Instructions

Returns a vehicle color.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden and supplies almost nothing. It does not disclose whether the returned value is random, deterministic, a fixed enum member, or a human-readable name versus a hex code. For a zero-argument generator-style tool, randomness/determinism is the single most important behavioral fact and it is absent.

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 no filler and the key information front-loaded. It is not bloated, though the extreme brevity is closer to under-specification than to disciplined concision.

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?

There is no output schema and no annotations, so the description is the only place the return value could be characterized, and it is not: format (hex, CSS name, RGB tuple), range, and whether the result varies between calls are all unstated. For a tool whose entire contract is its return value, that is a meaningful gap.

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 meaning for the description to add; the baseline for a parameterless tool applies. The empty schema with additionalProperties:false is fully self-explanatory.

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?

The description states a specific verb and resource ("Returns a vehicle color"), so the basic intent is readable. However, it does not distinguish this tool from adjacent color/data tools (e.g. color-human, color-rgb, vehicle-model now in the sibling list), nor does it say whether the value is drawn from a fixed list or generated. The purpose is identifiable but thin.

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, no mention of alternatives, and no statement of any prerequisite or side condition. The agent must infer entirely from the name that this is the vehicle-colour source rather than a general colour formatter.

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