Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

music-album

Generate random album names for test data, mock content, or music-themed prompts when you need believable sample titles.

Instructions

Returns a random album name.

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

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?

With no annotations, the description must carry the behavioral burden; it discloses the two most important traits — the output is a name and it is randomized per call. It does not say whether calls are seeded/repeatable, which name pool is used, or that the operation is side-effect free, but for a parameterless generator the disclosed behavior is roughly sufficient.

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 or redundant restatement of the tool name. There is nothing to trim and the key information arrives immediately.

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?

This is a trivially simple, parameterless tool and the description states what is returned, which is the main thing an agent needs; with no output schema, saying it returns an album name (a string) is adequate. Minor gap: no note on the name source or on determinism, though neither is required to call it correctly.

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-description baseline of 4 applies and there is no parameter meaning the description needs to add. Nothing in the description conflicts with the empty input schema (additionalProperties: false).

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 sentence names a specific verb ("Returns") and resource ("album name") plus the qualifying trait "random", so the agent knows exactly what comes back. It does not distinguish itself from sibling generators like music-artist or music-songName, leaving the agent to infer the split from the names alone.

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 explicit when-to-use guidance, no exclusions, and no named alternative. The only steer is the word "random", from which an agent can loosely infer this is for placeholder/sample data, but nothing states that or contrasts it with the sibling music-* generators.

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