Skip to main content
Glama

Sudan Atlas

Boundary of a state or locality

get_boundary

The boundary as a GeoJSON Feature (EPSG:4326) with the place's properties. 'light' is small and enough for most maps; 'medium' is more detailed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pcode": "<pcode>"
    },
    "name": "get_boundary"
  }
}

Input Schema

NameRequiredDescriptionDefault
pcodeYes
resolutionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the return format (GeoJSON Feature), CRS (EPSG:4326), and that place properties are embedded. It does not say what happens when a boundary is unavailable for a given place, whether geometry is simplified, how large responses get at 'medium', or whether administrative hierarchy affects the result. Some real value added, but important behavioral gaps remain.

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?

Two short sentences with the return type front-loaded and the resolution trade-off immediately after; there is no filler. The phrase 'with the place's properties' is slightly vague about what properties are included, but that is a minor cost.

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?

There is no output schema, so the description is the only source for return-value expectations, and it does cover format and CRS. However, for a geometry-retrieval tool it omits failure behavior for places without boundaries, the geometry type (Polygon vs MultiPolygon), and any sense of response size at 'medium'. Adequate but with clear gaps.

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 0%, so the description must compensate for both parameters. It explains the resolution enum well ('light' small and enough for most maps, 'medium' more detailed), but says nothing about pcode — its SD-prefixed format, what kind of place it identifies, or whether the code must correspond to an existing place. Half the parameters gain meaning, half do not.

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+resource outcome: it returns the boundary of a place as a GeoJSON Feature in EPSG:4326, with the place's properties. That is clear enough to distinguish it from siblings like get_place or search_places, which return place records rather than geometry. It stops short of naming an alternative explicitly, so it is clear but not sibling-differentiating at the top level.

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 only guidance given is about choosing between the two resolution values ('light' is enough for most maps, 'medium' is more detailed), which is useful but is parameter guidance rather than tool-selection guidance. Nothing says when to call this instead of get_place, or under what conditions a boundary is the right output. Usage is implied by the name and purpose rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.