Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

company-catchPhraseNoun

Returns a random catch phrase noun for company slogans or taglines. Use it to generate sample marketing text or mock content for end-user display.

Instructions

Returns a random catch phrase noun 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-catchPhraseNoun"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.6/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 burden. It discloses the key behavioral trait — the return value is random and display-safe — but says nothing about repeatability, whether output is a bare string or wrapped object, or whether values are guaranteed non-empty. For a trivial zero-argument generator this is acceptable, but a gap remains around return shape.

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?

One short sentence with no filler, front-loading the verb and the exact resource returned. Nothing could be removed without losing information.

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?

With no output schema, no annotations, and no parameters, the description is the only source of truth about the response — and it never specifies the format (bare string vs. JSON object), capitalization, or approximate length. It is otherwise proportionate to a trivial generator.

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, which is the baseline-4 case: there is nothing for the description to clarify beyond the empty schema. No parameter meaning is missing.

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 noun.' The word 'noun' clearly separates it from the adjective, descriptor, and verb siblings in the catchPhrase/buzz family. It stops short of naming any sibling explicitly, so it lands at 4 rather than 5.

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?

The clause 'can be displayed to an end user' implies the intended use (safe placeholder/sample text for display), but the description never says when to pick this over company-catchPhrase, company-catchPhraseAdjective, or word-noun. Usage is only inferable, not stated.

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