Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

company-catchPhraseAdjective

Generates a random catch phrase adjective for end-user display, providing varied descriptors to build company catchphrase content.

Instructions

Returns a random catch phrase adjective that can be displayed to an end user.

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": "company-catchPhraseAdjective"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.5/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 behavioral burden. It does disclose the key trait that output is random (non-deterministic across calls) and that the value is end-user facing, but says nothing about return type, possible empty results, or side effects. For a stateless zero-argument generator that is a moderate gap rather than a severe one.

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 no redundant wording. The trailing clause 'that can be displayed to an end user' is the only part that is not strictly necessary, but it does add context.

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?

The tool is trivial (no inputs, no annotations, no output schema), so completeness demands are low. Still, with no output schema the description should state the shape of the return value (a plain string adjective) and whether repeated calls vary; it only gestures at this via 'random'.

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 and the baseline for empty schemas applies. Nothing in the description misleads about inputs.

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 catch phrase adjective'. An agent knows exactly what it produces. It does not, however, distinguish itself from adjacent generators such as company-catchPhraseNoun, company-catchPhraseDescriptor, or word-adjective, so the boundary between siblings must be inferred from the names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'That can be displayed to an end user' implies the intended use case (placeholder/seed display text), which is better than nothing. There is no explicit when-to-use clause, no exclusion of alternatives, and no note on repeated calls returning different values, so usage is only weakly guided.

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