Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

word-conjunction

Returns a random conjunction, optionally filtered by word length or length options, to generate fake grammatical data for tests, mock content, and sample text.

Instructions

Returns a random conjunction.

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

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, the description carries the full behavioral burden, yet it only says the result is random. It does not explain what happens when a length constraint cannot be satisfied (despite the schema's 'fail'/'closest'/'shortest'/'longest' strategies), whether an error is raised, or what the return value looks like.

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?

The single sentence is front-loaded, unambiguous, and free of filler. It is arguably too terse, but the terseness gaps are captured under other dimensions rather than being wasted wording.

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 simple one-optional-parameter generator with full schema coverage, the definition is minimally adequate. However, with no output schema and no annotations, a sentence about the return type or the effect of the length/strategy options would have closed the remaining gap.

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 coverage is 100%, so the nested 'length' and 'strategy' options are already fully documented in the schema. The description adds no meaning beyond that, but with complete schema documentation the baseline of 3 is appropriate.

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 ('Returns') and resource ('a random conjunction'), so an agent immediately knows this generates a conjunction word. It does not explicitly differentiate itself from the many sibling word generators (word-adjective, word-noun, etc.), though the word type in the name and description makes the distinction obvious.

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 choose this tool over the sibling word generators, nor any mention of the optional length/strategy options that would affect selection. The only implied usage is 'use this when you need a conjunction,' which the agent could already infer from the title.

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