Skip to main content
Glama

Sudan Atlas

Match a Sudanese place name

match_place_name

Match one state or locality name, in Arabic or English and any spelling, to its official P-code. Returns pcode (null when not confident), names, score 0-1, method (exact, variant, fuzzy, ambiguous, none) and up to three alternatives.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe place name as written, e.g. 'Elfasher' or 'الفاشر'
levelNo1 for states, 2 for localities; leave out if unknown
state_hintNoThe state, as a name in any spelling or a P-code such as SD02

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and largely meets it: it enumerates the return fields, explains that pcode is null on low confidence, and lists the method values (exact, variant, fuzzy, ambiguous, none) plus the cap of three alternatives. That is unusually rich behavioral disclosure in the absence of an output schema; the only gap is that it never states this is a side-effect-free read operation or mentions any cost/rate limits.

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?

Two tightly packed sentences with the action first and the return contract second; there is no filler, and the parenthetical enumerations replace what would otherwise be a paragraph.

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?

Since there is no output schema, the description usefully doubles as a return-value contract and confidence model, which is the main thing an agent needs here. It falls slightly short on guidance for combining level and state_hint to improve matching, but the schema covers those parameters individually.

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 name, level, and state_hint are already documented per-parameter, making 3 the baseline. The description adds only that names may be Arabic or English in any spelling, and says nothing about how level or state_hint disambiguate a match beyond what the schema already says.

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 gives a specific verb and resource ('Match one state or locality name ... to its official P-code') and scopes it to a single name, which implicitly separates it from the plural sibling match_place_names. It never states that distinction explicitly, so an agent must infer the singular/batch split from the sibling name alone.

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?

Usage is implied rather than stated: accepting 'any spelling' in Arabic or English signals this is the fuzzy/robust resolver, but there is no explicit when-to-use versus get_place or search_places, and no when-not condition. The 'null when not confident' note hints at a fallback path without saying what to do next.

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.