Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

word-adverb

Generate a random adverb for filler text, grammar examples, or testing, with optional length constraints and fallback strategies.

Instructions

Returns a random adverb.

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

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?

No annotations are supplied, so the description carries the full burden. It discloses that output is random, but says nothing about the return type (string vs. array), the failure behavior implied by the 'strategy' option, or whether the length constraint can alter or fail the result.

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 wasted words. It is efficient, though the brevity leaves little structure to speak of.

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 one-optional-parameter generator with no output schema, the essentials are covered by the schema. However, an agent still learns nothing about the returned shape or how the length options affect a 'random' pick, which the description could cheaply supply.

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%, with the nested length/strategy semantics fully documented in the schema itself. The description adds no parameter meaning beyond that, so baseline 3 applies.

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 ("Returns a random adverb"), and the part-of-speech naming convention makes it distinguishable from siblings like word-noun and word-verb. It stops short of explicitly differentiating itself from those siblings, but the resource is unambiguous.

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?

The description contains no when-to-use or when-not-to-use guidance, and names no alternatives. Usage is only inferable from the tool's self-evident single purpose, not from any stated context.

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