Skip to main content
Glama

Sudan Atlas

Details of a state or locality

get_place

Official names, level, parent state, localities (for a state), area in km² and estimated population (COD-PS 2025, mid-2025) for a P-code.

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_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
pcodeYesA P-code such as SD02 or SD02114

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 must carry the behavioral load; it does convey data provenance (COD-PS 2025, mid-2025) and that the payload is descriptive metadata rather than geometry, implying a read-only lookup. It does not state read-only semantics explicitly, nor what happens with a malformed or unknown P-code, nor whether population is estimated versus a census figure beyond the parenthetical source.

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?

A single dense sentence that front-loads the returned fields and ends with the input key. Every clause names a distinct returned attribute; nothing is repeated or wasted.

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

Completeness4/5

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

For a one-parameter lookup with no output schema, the description serves as an adequate return-value contract by listing the fields and their units, which is the main risk area. Minor gaps remain around invalid-P-code behavior and whether nested localities are full records or just names.

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 coverage is 100% and the pattern plus example (SD02 or SD02114) already define the parameter, so the baseline is 3. The description adds only marginal meaning by implying the two-level P-code structure (state vs. locality) through 'localities (for a state)', but never explains the format itself.

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 enumerates the exact resource returned — official names, level, parent state, localities, area in km², population — keyed by P-code, so the resource is unmistakable. It falls short of 5 because it is a noun phrase with no verb and never distinguishes itself from siblings like get_boundary or search_places.

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 when-to-use statement, no prerequisite (that you must already hold a P-code), and no mention of alternatives such as match_place_name for resolving names to P-codes or get_boundary for geometry. The only implied guidance is that a P-code input is required, which the schema already states.

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.