Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

food-description

Generates a random dish description for use as sample or placeholder content in menus, mockups, and test data.

Instructions

Generates a random dish description.

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": "food-description"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3/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 behavioral burden, and the single word "random" is the only trait disclosed — it usefully implies non-deterministic, repeat-call-varying output. Nothing is said about output length, style, cuisine scope, or determinism/seed control, and with no output schema the return shape is entirely unknown.

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?

One short, front-loaded sentence with zero filler — the core purpose lands immediately. It is efficient, though its extreme brevity leaves no room for any structuring of usage or output expectations.

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 the surface area is small, but with no annotations and no output schema the definition never tells the agent what a "dish description" looks like (sentence vs. paragraph, cuisine-specific or generic). That missing return expectation is the main incompleteness.

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 is empty, so there is no parameter meaning to convey; the baseline of 4 applies. The description correctly implies no inputs are needed.

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?

"Generates a random dish description" states a specific verb (generates) and a specific resource (random dish description), so the operation is unmistakable. It does not, however, distinguish itself from look-alike siblings such as food-dish or commerce-productDescription, which is the one gap keeping this below a 5.

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 guidance on when to reach for this tool versus food-dish, food-ingredient, or the commerce product-description sibling, and no stated preconditions. The agent must infer usage entirely from the name and one-line description.

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