Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

location-direction

Returns a random cardinal or ordinal direction such as northwest or east, with an option to get abbreviated forms like NW or E.

Instructions

Returns a random direction (cardinal and ordinal; northwest, east, 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-direction"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it does disclose the key behavioral trait: the result is random and spans both cardinal and ordinal directions. It omits distribution/seed details and does not state that the tool has no side effects, but for a trivial value generator that is a minor gap.

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, front-loaded with the verb and result type, with examples inline. Nothing is wasted and nothing essential is buried.

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-required-parameter tool with no output schema and no annotations, the description covers what it returns and the shape of the values via examples. No output schema exists, so the description should ideally pin down the exact return string format, which it only does loosely.

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?

There is a single optional parameter at 100% schema description coverage, so the schema already explains 'abbreviated' fully. The description adds nothing beyond it, which matches the baseline of 3.

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 direction') and adds parenthetical examples ('northwest, east') plus the cardinal/ordinal scope. That scope implicitly separates it from the sibling location-cardinalDirection and location-ordinalDirection, though the description never names them.

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 when-to-use guidance. The word 'random' hints that this is the non-deterministic option versus the deterministic cardinal/ordinal siblings, but no alternative is named and no exclusion or precondition is given.

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