Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

animal-bear

Returns a random bear species for mock data, demos, or placeholder content.

Instructions

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about the shape of the return value, whether a fixed set of species is sampled with replacement, or whether repetition can occur. The only behavioral fact given is randomness, which is already implied by "random" in a generator family.

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 front-loaded sentence with no filler. For a zero-argument generator there is nothing to cut and nothing buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a trivial zero-param, no-output-schema tool, a one-line description is close to proportionate, and no return-value spec is strictly required. What is missing is the surrounding fact that this is synthetic/fixture data, which would let an agent decide whether it belongs in a real-data path.

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 meaning to convey and the baseline applies. The description correctly implies no input is needed, though it never says so explicitly.

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 bear species") so the agent knows exactly what it produces, and the sibling naming pattern (animal-lion, animal-dog, etc.) makes the scope distinction obvious without needing to be spelled out. It falls short of a 5 only because it never frames this as a mock/faker-style data generator, which is the family's actual purpose.

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?

There is no guidance on when to reach for this over animal-type or a specific species tool, and no mention of the intended context (seeding test data, placeholder values). The agent must infer usage purely from the one-line purpose.

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