Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

location-longitude

Generates a random longitude within specified minimum and maximum bounds, with adjustable decimal precision for realistic test coordinates.

Instructions

Generates a random longitude.

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

Input Schema

NameRequiredDescriptionDefault
maxNoThe upper bound for the longitude to generate.
minNoThe lower bound for the longitude to generate.
precisionNoThe number of decimal points of precision for the longitude.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses the essential trait (randomness) but says nothing about default bounds when min/max are omitted, whether bounds are inclusive, whether the distribution is uniform, or the valid longitude range of -180 to 180.

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 well-formed sentence with the core action front-loaded and no wasted words. Its brevity is appropriate, though it borders on under-specification rather than tightness.

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?

For a generator with three optional parameters, no required inputs, no annotations, and no output schema, the description leaves key behavior undefined: default range, output format, and validity constraints. An agent could call it but cannot predict what it returns when min/max are omitted.

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%, so all three parameters (min, max, precision) are already documented in the schema. The description adds no meaning beyond that, so the 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?

The description gives a specific verb and resource ('Generates a random longitude'), which is clear and distinguishes it by name from the sibling 'location-latitude'. It stops short of explicitly contrasting itself with that sibling or stating what makes the output a valid longitude.

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, no mention of the alternative latitude generator, and no indication of when bounded generation is preferable to unbounded. An agent must infer purpose entirely from the single sentence.

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