Skip to main content
Glama

Coordinates

by io.github.pipeworx-io

Centroid

centroid
Read-onlyIdempotent

Average (spherical) center of a list of lat/lon points. points is an array of {lat, lon}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pointsYesArray of {lat, lon} objects.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "points": [
+      {
+        "lat": 40.7128,
+        "lon": -74.006
+      },
+      {
+        "lat": 34.0522,
+        "lon": -118.2437
+      },
+      {
+        "lat": 41.8781,
+        "lon": -87.6298
+      }
+    ]
+  },
+  {
+    "points": [
+      {
+        "lat": 51.5074,
+        "lon": -0.1278
+      },
+      {
+        "lat": 48.8566,
+        "lon": 2.3522
+      }
+    ]
+  }
+]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Description matches annotations (readOnly, idempotent). No additional behavioral details beyond what annotations provide, but no contradiction.

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?

Two sentences, no wasted words. Purpose and parameter clearly stated in minimal space.

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

Completeness3/5

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

No output schema, but tool is simple. Description could mention return format (single {lat,lon}) for completeness. Adequate but not thorough.

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 already fully describes 'points' parameter (100% coverage). Description only repeats schema info, adding no new meaning.

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?

The description clearly states the tool computes the average (spherical) center of lat/lon points. It distinguishes from sibling 'midpoint' by specifying spherical calculation.

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?

No guidance on when to use this tool vs alternatives like 'midpoint'. Lacks explicit when-to-use or when-not-to-use context.

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

All Coordinates toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation3/5

Many tools have overlapping purposes (e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded are nearly identical; bet_research and polymarket_edges both analyze Polymarket markets). Descriptions are detailed but the sheer number of similar tools creates ambiguity for agents.

Naming Consistency4/5

Most tools follow a verb_noun pattern (e.g., list_subscriptions, create_subscription), but a few use noun_verb (bet_research) or are standalone nouns (centroid, midpoint). Overall, the pattern is fairly consistent despite minor deviations.

Tool Count3/5

35 tools is on the high side for an MCP server. The scope is broad (data access, prediction markets, geospatial, memory, subscriptions), so each tool earns its place, but the number is borderline for coherence.

Completeness4/5

The tool set covers a wide range of functionalities: data querying, entity profiles, comparisons, prediction market analysis, geospatial, memory, subscriptions, etc. Minor gaps exist (no batch operations or data export), but the core workflows are well-supported.

Resources