Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

animal-cetacean

Returns a random cetacean species for generating fake animal data or testing cetacean-related features.

Instructions

Returns a random cetacean species.

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": "animal-cetacean"
  }
}

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 provided, so the description carries the full burden. It discloses the key trait, that the selection is random, but says nothing about the return shape (a plain string versus a structured object) or about the breadth of the species pool, leaving an agent guessing about the output.

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 short sentence with no filler, and the verb-plus-resource structure is front-loaded. It is appropriately sized, though the sentence could add one clarifying phrase about the return value without becoming bloated.

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 annotations, no output schema, and no parameters, the description is the only source of behavioral information, and it leaves the return format unspecified. For such a simple tool, the definition is barely adequate rather than fully complete.

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 nothing for the description to explain beyond the schema. The baseline for a parameterless tool is 4, and the description does not introduce any confusion 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?

The description states a specific verb and resource: it returns a random cetacean species. That is enough to distinguish it from the sibling generators (animal-bear, animal-cat, etc.) by subject matter, though it never explicitly names an alternative or clarifies the less common taxonomic term 'cetacean' (whales, dolphins, porpoises).

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?

Usage is only implied: an agent should call it when it needs a randomly chosen cetacean species. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to sibling tools, but the zero-parameter generator semantics are simple enough that the gap is small.

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