Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

vehicle-vehicle

Generates a random vehicle record for testing, prototyping, or populating mock datasets with realistic vehicle data.

Instructions

Returns a random vehicle.

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

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?

With no annotations, the description carries the full disclosure burden. It does contribute one real behavioral fact — the result is randomized and therefore non-deterministic — but says nothing about what the returned object contains, whether any fields are guaranteed, or whether repeated calls differ.

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 zero filler. It is efficient, though its brevity edges into under-specification rather than true conciseness.

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 source of information about the return value — yet it never describes the shape or fields of the returned vehicle. For a zero-parameter generator whose entire value is its output, that leaves a significant 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 input schema takes zero parameters at 100% coverage, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter guidance is needed.

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 random vehicle" gives a verb and a resource, so the basic action is clear. But it never says what a "vehicle" object is (a composite record vs. a single field like the sibling vehicle-vin or vehicle-model), and it draws no boundary against the many sibling vehicle-* tools that return individual attributes.

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, and no mention of alternatives such as vehicle-model or vehicle-type for agents that need a specific field rather than a whole random record. The intended context (e.g., seeding mock/test data) is only implied by the word "random".

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