Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

food-adjective

Generates a random dish adjective for fake menus, food data, and testing. Supplies descriptive terms without manual selection.

Instructions

Generates a random dish adjective.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the key behavioral trait that the output is random (non-deterministic), but it says nothing about the return shape, whether repeated calls can repeat values, or that it is a pure side-effect-free read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no redundant or filler wording. For a zero-argument generator this is appropriately sized and immediately actionable.

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?

For a trivial parameterless tool the description is close to sufficient, but with no output schema the agent is left guessing the return type (a bare string versus an object wrapping the adjective). That single missing detail is the only real 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 semantics to explain; the baseline for a parameterless tool applies. Nothing in the description misleads about inputs, and the empty schema is consistent with the described behavior.

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?

States a specific verb and resource: "Generates a random dish adjective." An agent can tell this produces a single adjective for food/dish naming. It does not, however, distinguish itself from the adjacent siblings such as commerce-productAdjective or word-adjective, so the agent must rely on naming conventions alone to pick between adjective generators.

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 use this versus the many sibling adjective/word tools (commerce-productAdjective, company-catchPhraseAdjective, word-adjective) or the food-specific siblings like food-description and food-dish. Usage must be inferred entirely from the tool name.

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