Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

location-cardinalDirection

Generate a random cardinal direction, such as north, east, south, or west, with an option to return abbreviated values like N or E.

Instructions

Returns a random cardinal direction (north, east, south, west).

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": "location-cardinalDirection"
  }
}

Input Schema

NameRequiredDescriptionDefault
abbreviatedNoIf true this will return abbreviated directions (N, E, etc).

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 most important trait: the result is random, not derived from input. It does not say whether the distribution is uniform, whether repeated calls can repeat values, or that no external state or auth is involved, which would be useful for a randomization tool.

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?

One sentence, no padding, and the return values are listed immediately so the agent can see the output domain up front.

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-required-parameter random generator with no output schema, the description covers the essential return value and the randomness. The only gaps are the undocumented output-shape details (abbreviated vs full form interaction) and differentiation from near-identical siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single 'abbreviated' parameter is fully documented in the schema with an example, so the baseline of 3 applies. The description adds nothing about the parameter, but it does not need to.

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 gives a specific verb and resource ('Returns a random cardinal direction') and even enumerates the four possible values, so the agent knows exactly what comes back. It does not distinguish itself from the sibling tools location-direction and location-ordinalDirection, which sound very similar, so the agent must infer the difference from name 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 statement of when to use this versus location-direction or location-ordinalDirection, and no context about appropriate call scenarios. The agent is left to infer usage purely from the word 'cardinal' in the name.

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