Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

location-ordinalDirection

Generate a random ordinal direction such as northwest or southeast for testing or data generation. Optionally return abbreviated forms like NW or SE.

Instructions

Returns a random ordinal direction (northwest, southeast, etc).

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

Input Schema

NameRequiredDescriptionDefault
abbreviatedNoIf true this will return abbreviated directions (NW, SE, 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 provided, so the description carries the disclosure burden. It does usefully reveal that the output is random (non-deterministic), but it says nothing about distribution, whether repeated calls differ, or return format. Adequate but thin for a tool with zero annotation coverage.

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 short sentence, front-loaded with the action and result, with examples that remove ambiguity about 'ordinal'. Nothing extraneous.

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 generator with no output schema, the description plus schema covers what an agent needs to call it correctly. Only the randomness semantics and output shape are left implicit.

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, including an example (NW, SE). The description adds no parameter meaning beyond that, so baseline 3 applies.

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 concrete verb and resource: 'Returns a random ordinal direction', reinforced by parenthetical examples (northwest, southeast). The term 'ordinal' together with those examples distinguishes it from a plain direction/cardinal generator, though no sibling is named explicitly.

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 use this versus location-cardinalDirection or location-direction, and no stated preconditions. The only hint is the word 'ordinal' in the name and examples, which an agent must infer.

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