Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

vehicle-model

Generates a random vehicle model name for mock records, test datasets, or placeholder content.

Instructions

Returns a vehicle model.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.4/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 behavioral burden, yet it discloses nothing beyond the existence of a return value. It does not say whether the result is a fixed lookup, a randomly generated value, a localized string, or a list, nor what format the model name takes — all critical for a zero-parameter generator-style tool.

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?

It is a single sentence with no wasted words and the key noun is front-loaded, so it is structurally clean. However, the brevity comes from under-specification rather than from efficient compression of real information.

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?

With no annotations and no output schema, the description is the only source of information about the return value, and it says nothing about shape, example format, or determinism. For an extremely simple tool this is not catastrophic, but the definition still leaves the agent guessing at what comes back.

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 and the schema coverage is complete, so there is no parameter meaning for the description to add. The baseline for a parameterless tool applies.

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

Purpose2/5

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

"Returns a vehicle model" restates the tool name (vehicle-model) almost verbatim, adding only the verb "Returns." It gives no signal to distinguish this from adjacent siblings such as vehicle-manufacturer, vehicle-type, or vehicle-vehicle, so an agent must guess which of the vehicle-* tools yields a model name.

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 alternatives, and no exclusions. The agent is left to infer that this is the model-name lookup among the vehicle-* family purely from the name itself.

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