Skip to main content
Glama

Sudan Atlas

List states or localities

list_places

All 19 admin-1 units (18 states and the Abyei PCA area), or the localities of the whole country or of one state.

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": {
      "level": "<level>"
    },
    "name": "list_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYes
state_pcodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/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; it does add real value by disclosing the exact result-set scope (all 19 admin-1 units incl. Abyei, or localities for country vs. one state), which implies result size can vary widely. It says nothing about return format, identifiers, or pagination/limits for the nationwide localities case, and no read-only/safety signal is given.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence with no filler, but it is elliptical to the point of being cryptic — it opens with 'All 19 admin-1 units' rather than naming the operation, and jams two distinct output modes into one clause with an 'or'. Slightly more structure would make the two modes easier to act on.

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

Completeness2/5

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

For a two-parameter tool with no annotations and no output schema, the description leaves key gaps: what fields come back per place, how the two modes are selected, and what happens when level=2 is used without state_pcode. It is adequate as a hint about coverage but not sufficient to call the tool correctly without inspecting the schema.

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

Parameters2/5

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

Schema description coverage is 0% and there are two parameters, so the description must compensate for 'level' (const 1 or 2) and 'state_pcode' (pattern ^SD\d{2}$) — yet neither is named. The reader can only indirectly infer that level 1 yields admin-1 units and level 2 yields localities, and that state_pcode narrows the second case; the pcode format and the fact that state_pcode is optional are never explained.

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

Purpose3/5

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

The sentence conveys the resource (admin-1 units and localities) and enumerates the top level precisely (18 states plus Abyei PCA), so an agent can tell this is a geographic reference list. However, it never states a verb or that it is a listing/retrieval operation, and it draws no contrast with siblings such as search_places or get_place, so the operation itself is only implied by the name.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of the sibling tools. The only hint is the disjunction between 'admin-1 units' and 'localities ... of one state', which hints at a scope choice but never says which situation selects which.

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.