Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

music-genre

Returns a random music genre for testing, prototyping, or populating sample content with varied genre data.

Instructions

Returns a random music genre.

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": "music-genre"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.4/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 burden, and it does disclose the key behavioral trait: the output is non-deterministic ("random"). It does not state whether values can repeat across calls, what the domain of genres is, or whether the call has any side effects, though for a zero-parameter pure lookup these gaps are modest.

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 front-loaded sentence with no filler or redundancy, which is well matched to a trivial tool. It leaves slight room for a short clause about the return form without becoming bloated.

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 zero-parameter, annotation-free generator with no output schema, the description covers what the tool does and that the result is random, which is the core information needed to call it. It stops short of describing the shape of the returned value (bare genre string versus object) or the genre vocabulary, the only remaining ambiguities.

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 and schema coverage is 100%, which lands at the baseline 4; there is no parameter meaning for the description to add. Nothing in the description conflicts with the empty input schema.

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 pairs a specific verb ("Returns") with a specific resource ("a random music genre"), so the agent knows exactly what it produces. The "music" qualifier implicitly separates it from sibling book-genre, but no explicit sibling differentiation is offered.

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 call this versus alternatives, nor any exclusions or context. The agent must infer from the name alone that this is a sampling helper rather than a lookup keyed on input.

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