Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

word-interjection

Generates a random interjection, optionally constrained by word length, for filler text, dialogue, or test data.

Instructions

Returns a random interjection.

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": "word-interjection"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNoThe expected length of the word or the options to use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations at all, the description carries the full disclosure burden and delivers only the word "random". It never says what happens when no word matches the requested length, even though the schema's "strategy" enum includes "fail", which strongly implies an error path an agent should anticipate.

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 six-word sentence with the resource front-loaded and no filler. Nothing is padded or repeated, and it is sized correctly for a trivial generator.

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, yet the description says nothing about the returned value's shape, the options parameter, or the no-match behavior. For a tool with a non-trivial nested options object and no structured supporting metadata, the description leaves too much unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents the length, min/max and strategy fields in detail, and the description adds nothing on top. Baseline 3 applies: the parameter is documented, but the description contributes no extra meaning about accepted forms or fallback 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?

"Returns a random interjection" states a specific verb (returns) plus a precise resource (interjection), which lets an agent distinguish it from word-noun, word-verb and other siblings without opening a schema. It stops short of explicitly contrasting itself with those siblings, so it is clear but not maximally differentiating.

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 explicit when-to-use, when-not-to-use, or alternative routing guidance. The purpose is self-evident enough that an agent can infer a use case, but nothing tells it when to prefer this over picking a different word-type tool, and nothing explains when the options parameter matters.

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