Hopi

Random coordinates generator

hopi_random_coordinates

Read-onlyIdempotent

Generate random geographic coordinates that are uniform by surface area across the globe (points are not bunched at the poles). Returns latitude and longitude in decimal degrees. Source: https://hopi.co.uk/random-coordinates/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`decimals`	No	Decimal places for each coordinate, 2 to 6 (default 4)
`quantity`	No	How many points to generate, 1 to 100 (default 1)

Output Schema

TableJSON Schema

Name	Required	Description
`points`	Yes
`summary`	Yes
`source_url`	Yes	The tool's page on hopi.co.uk (cite or open to check the figure)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026
- addedOutput schema / required
```
Added value: +[
+  "points",
+  "source_url",
+  "summary"
+]
```
First observedSep 20, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark the tool as read-only and non-destructive. The description adds useful behavioral context beyond annotations: the uniform-by-surface-area sampling method, the pole-avoidance property, and decimal-degree output. The source link also provides transparency about the implementation origin.

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?

The description is short, front-loaded with the action, and every sentence adds value: generation behavior, output format, and data source. It avoids filler and redundant restatement of the tool name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero required parameters, full schema coverage, safety annotations, and an output schema, the description provides everything needed: what is generated, how points are distributed, and the coordinate format. There is no meaningful missing context for correct invocation.

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?

Input schema coverage is 100%, and both parameters already have clear descriptions, defaults, and min/max constraints. The tool description adds no significant parameter-level meaning beyond confirming decimal degrees, so the schema carries the semantic burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Generate random geographic coordinates'. It also includes the key differentiator (uniform by surface area, not bunched at poles) and the output format (latitude and longitude in decimal degrees), which clearly separates it from sibling random generators.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the intended use obvious: generating random global coordinates. It does not explicitly name alternatives or list exclusions, but the scope is so specific that an agent can reliably select this tool over random_number_generator or random_colour_generator without additional guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Hopi tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?