Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

animal-cat

Returns a random cat breed for generating sample data, testing, or placeholder content.

Instructions

Returns a random cat breed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.2/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 disclosure burden. It does add one real trait beyond the name by saying the result is "random," implying non-determinism and repeated calls yielding different values, but it omits the return shape, whether a fixed breed list is used, and how many breeds are in the pool. There is no output schema to fall back on, so the return format is entirely undocumented.

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?

A single short sentence with the essential fact front-loaded and no padding, filler, or hedging. Nothing in it could be removed without losing meaning.

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 zero-parameter, zero-annotation tool with no output schema, the only meaningful gap is what a caller receives back, and the description leaves that to inference (a single breed name string versus an object with metadata). It is otherwise adequate for the tool's low complexity, but one clause naming the return value would have closed the gap.

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 the schema is empty and complete by definition, and there is nothing for the description to disambiguate. Baseline for a parameterless tool applies.

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?

Specific verb plus resource: "Returns a random cat breed." An agent can immediately tell it produces a cat breed rather than a bear, bird, or dog entry, matching the per-animal pattern of its siblings. It stops short of a 5 because it never states how that differs in use from neighbors like animal-petName or animal-type, which also return animal-related data.

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 when-to-use, when-not-to-use, or alternative tool is named. The description does not tell the agent whether this is for populating sample data, seeding a UI, or answering a breed question, nor does it point to animal-type or animal-petName for related needs. Usage is only inferable from the name itself.

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