Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

location-latitude

Generates a random latitude within specified minimum and maximum bounds, with configurable decimal precision for geolocation testing and mock data.

Instructions

Generates a random latitude.

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

Input Schema

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

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?

No annotations are supplied, so the description carries the full burden. It discloses that output is random, which is useful, but says nothing about defaults when min/max/precision are omitted, what happens if min > max, or whether values are clamped to the valid latitude range of -90 to 90.

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 front-loaded sentence with zero waste. It is arguably over-terse, but nothing is redundant or buried.

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?

All three parameters are optional and there is no output schema or annotation coverage, so the description should at least explain the no-argument default behavior and the valid coordinate range. Neither is present, leaving an agent unable to predict results when parameters 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 (max, min, precision) are already documented in the schema. The description adds no extra meaning such as default bounds, valid latitude limits, or whether precision affects rounding versus truncation; 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 states a specific verb and resource ('Generates a random latitude'), so an agent knows exactly what the tool produces. It does not differentiate from the sibling 'location-longitude', which is presumably the identical generator for the other coordinate, nor does it note that output is bounded to the latitude range.

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 when to prefer 'location-longitude' or 'location-nearbyGPSCoordinate', and no stated conditions or prerequisites. The agent must infer usage entirely from the one-line purpose.

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