Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

word-preposition

Returns a random preposition, with optional length constraints and fallback strategies, to generate sample grammar or placeholder text in test data.

Instructions

Returns a random preposition.

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

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 behavioral burden. 'Random' usefully discloses non-determinism, but nothing is said about the failure/closest/shortest/longest strategies exposed by the parameter, whether an empty result is possible, or what the response looks like — significant gaps for a generator with zero annotation coverage.

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 front-loaded sentence with no wasted wording. It is efficient, though its terseness is part of why behavioral and usage context are missing.

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?

A simple single-parameter generator with a fully documented schema and no output schema needs little prose, so this is close to adequate. However, with no annotations and no output schema, the description should at least hint at what a match-failure returns, which it does not.

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 single optional 'options' parameter, its nested length bounds, and the strategy enum are already fully documented in the schema. The description adds no meaning beyond that, which is acceptable at this coverage level but earns no extra credit.

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?

The description states a specific verb and resource ('Returns a random preposition'), which is unambiguous and lets an agent tell it apart from the adjacent word-adjective/word-noun/word-verb siblings by resource alone. It stops short of an explicit sibling comparison, but the noun identifies the output domain precisely.

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?

No guidance on when to use this versus the other word-* siblings, no prerequisites, and no mention of what happens if the length constraint cannot be satisfied. The agent must infer usage purely 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