Skip to main content
Glama

Geoboundaries

by io.github.pipeworx-io

Get Boundaries

get_boundaries
Read-onlyIdempotent

Get administrative boundary metadata for a country from geoBoundaries: unit count, year represented, source, license, and download URLs for full GeoJSON (gjDownloadURL), simplified GeoJSON (simplifiedGeometryGeoJSON), TopoJSON (tjDownloadURL) and a static zip. ISO3 is the 3-letter country code (USA, FRA, KEN, IND). ADM level: ADM0=country, ADM1=state/province, ADM2=county/district, ADM3/ADM4=finer, ALL=every level. Default product gbOpen is CC-BY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
admYesAdmin level: ADM0=country, ADM1=state/province, ADM2=county/district, ADM3, ADM4, or ALL.
iso3YesISO-3166-1 alpha-3 country code, e.g. "USA", "FRA", "KEN".
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": "ADM1",
+    "iso3": "USA"
+  },
+  {
+    "adm": "ADM2",
+    "iso3": "FRA",
+    "product": "gbHumanitarian"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral context by enumerating the exact metadata fields returned, listing download URL types, and noting the default product's CC-BY license—details beyond the annotations.

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 four sentences, each earning its place: purpose, ISO3 explanation, ADM level explanation, and product/license note. It is dense but not verbose, with clear front-loading of the core function.

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?

Without an output schema, the description thoroughly communicates the return payload (unit count, year, source, license, download URLs), fully explains all three parameters, and states defaults and licensing. It provides a complete picture of what the tool does and returns, leaving minimal ambiguity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions cover 100% of parameters, so the baseline is 3. The description adds value by providing concrete ISO3 examples, explaining ADM levels in a natural hierarchy, and clarifying the default product and license, enriching what the schema already provides.

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 opens with a specific verb and resource: 'Get administrative boundary metadata for a country from geoBoundaries'. It clarifies the return type (metadata with download URLs), distinguishing it from the sibling tool get_geometry which likely fetches geometry itself.

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

Usage Guidelines3/5

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

The description implies when to use the tool (when you need boundary metadata) and explains parameter semantics, but it does not explicitly mention alternatives or when not to use it. With get_geometry as a close sibling, a direct comparison would strengthen this dimension.

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