Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

animal-horse

Returns a random horse breed for populating mock data and testing animal-related features.

Instructions

Returns a random horse 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-horse"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.4/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 burden. It does disclose one real behavioral trait - the output is nondeterministic ('random') - but says nothing about the return type (plain string vs object), whether successive calls can repeat, or that the call is side-effect free. For a zero-risk generator the bar is low, yet the gaps above are real.

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 six-word sentence, front-loaded with the verb and containing no filler. Nothing 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 trivial zero-argument generator with no output schema, the description covers purpose but leaves the return shape undocumented. An agent knows what the tool produces conceptually ('a horse breed') yet not whether it receives a bare string or a structured object, which matters when no output schema exists to fill that hole.

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 input schema has zero properties and additionalProperties is false, so there is nothing for the description to explain. Baseline 4 applies for a no-parameter tool; the description correctly implies the call takes no arguments.

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 horse breed.' The resource word 'horse' cleanly separates it from the other animal-* siblings such as animal-dog or animal-bear, so an agent can select it without opening the schema. It stops short of 5 only because there is no explicit contrast with alternatives.

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 can infer this is a mock-data generator for producing a breed string, but the description never says when to use it (test fixtures, seeding sample data) or when not to. With no explicit routing between this and the other animal-* tools, the guidance is adequate but thin.

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