Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

person-zodiacSign

Returns a random zodiac sign to populate fake profiles, test data, or demo content.

Instructions

Returns a random zodiac sign.

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": "person-zodiacSign"
  }
}

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, and it discloses almost nothing beyond the word "random". It does not say whether randomness is uniform, whether repeated calls can repeat values, or whether output is affected by any seed/locale. For a data-generation tool the repeatability question is the practically important one and is left unanswered.

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 short sentence with zero filler, front-loaded on the action and result. It is economically written, though the brevity is close to under-specification rather than optimal density.

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

Completeness2/5

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

With no annotations and no output schema, the description is the only source of return-value information, and it never states the shape of the result (a bare sign name such as "Leo", an object, capitalization). For a trivial generator little is needed, but the one thing an agent cannot infer, the return format, is absent.

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 the schema is an empty object with additionalProperties false, so there is no parameter meaning for the description to add. Baseline 4 applies; nothing is missing on this dimension.

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 zodiac sign"), which is unambiguous and distinguishable from the sibling generators like person-firstName or person-gender. It stops short of explaining how it differs in scope from other person-* value generators, but the resource is concrete enough to select it without opening a schema.

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?

No explicit when-to-use statement, no exclusions, and no mention of alternatives. Usage is only implied: an agent needing a randomized zodiac value for sample/test data would infer it. For a zero-parameter generator the implied usage is close to self-evident, so a middle score rather than a low one.

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