Skip to main content
Glama

Geoboundaries

by io.github.pipeworx-io

Get Geometry

get_geometry
Read-onlyIdempotent

Fetch the actual simplified GeoJSON FeatureCollection geometry for a country/ADM level from geoBoundaries. WARNING: geometry payloads are large (a simplified national ADM1 set can be several MB); this only returns the simplified geometry and refuses payloads over ~4 MB — for those use get_boundaries and download the URL directly. Prefer get_boundaries unless you explicitly need the coordinates. Not valid for adm="ALL".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
admYesAdmin level (single level only; "ALL" is not supported here).
iso3YesISO-3166-1 alpha-3 country code, e.g. "FRA".
productNoBoundary product. gbOpen (default, CC-BY) | gbHumanitarian | gbAuthoritative.

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: +[
+  {
+    "adm": "ADM0",
+    "iso3": "KEN"
+  },
+  {
+    "adm": "ADM1",
+    "iso3": "IND",
+    "product": "gbOpen"
+  }
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare readOnly, openWorld, idempotent, and non-destructive hints. The description adds behavioral context beyond these: payloads can be several MB, the tool refuses payloads over ~4 MB, it returns only simplified geometry, and adm="ALL" is invalid. This enriches the annotation info without contradiction.

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?

The description is slightly long but every sentence adds critical information: what it fetches, size warning, size limit, alternative tool, and validity constraint. It is front-loaded with the main purpose and uses compact phrasing, though the warning could be considered a bit verbose for the score of 5.

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 the tool's complexity (large payloads, restriction on adm='ALL', relationship to get_boundaries), the description covers the return type, size behavior, refusal threshold, and usage context. No output schema exists, but the description sufficiently explains what is returned and the edge cases.

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 baseline is 3. The description does not add significant parameter-specific meaning beyond the schema; it focuses on response size and alternatives. It confirms product defaults indirectly via schema, but no extra semantic value is provided for the parameters themselves.

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 fetches simplified GeoJSON FeatureCollection geometry for a country/ADM level, using a specific verb and resource. It distinguishes itself from sibling get_boundaries by noting this tool only returns simplified geometry and explicitly recommends get_boundaries for other cases.

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

Usage Guidelines5/5

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

Explicit guidance is provided: 'Prefer get_boundaries unless you explicitly need the coordinates' and 'Not valid for adm="ALL"'. It also warns about payload size and directs users to get_boundaries for large payloads, covering both when-to-use and when-not-to-use.

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

All Geoboundaries 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.8/5.0
Disambiguation2/5

Many tools have overlapping or unclear purposes, e.g., multiple entity research tools (entity_profile, recent_changes, compare_entities, validate_claim) and several betting tools (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_kalshi_spread). The memory tools (remember, recall, forget) and generic lookup tools (ask_pipeworx, discover_tools) further blur boundaries, making it hard for an agent to consistently select the right tool.

Naming Consistency2/5

Tool names follow no consistent pattern: some use snake_case verbs (forget, recall, remember), others are noun phrases (entity_profile, recent_changes), and many have mixed conventions (ai_visibility_check, ask_pipeworx, bet_research). There is no clear verb_noun structure, and the naming style varies widely across the set.

Tool Count3/5

At 22 tools, the count is within a reasonable range, but the server's stated purpose ('Geoboundaries') is severely mismatched with the actual tool set, which covers data retrieval, betting, memory, and more. The number is not excessive for the breadth of functionality, but it feels bloated for a server that should be focused on geographic boundaries.

Completeness1/5

The server is named 'Geoboundaries' but only provides two boundary-related tools (get_boundaries, get_geometry). The remaining 20 tools are unrelated, covering general data access, betting arbitrage, and memory operations. This leaves massive gaps for the implied domain (no tools for boundary editing, search by location, or other geographic operations) while over-supplying tools for unrelated tasks.

Resources