Skip to main content
Glama

Sudan Atlas

Match many Sudanese place names

match_place_names

Match up to 1,000 names at once (for example a spreadsheet column). Each item can carry its own state hint. Results are in the same order as the input.

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

Input Schema

NameRequiredDescriptionDefault
levelNo1 for states, 2 for localities; leave out if unknown
namesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the behavioral burden itself. It usefully discloses the 1,000-name batch limit and that results preserve input order, but it does not explain what a match result contains, how unmatched names are handled, or whether the operation has side effects.

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?

Three short sentences with no wasted wording, front-loading the batch capacity and then covering per-item hints and result ordering. The structure is clear and directly useful for an agent deciding whether to call it.

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?

The tool is moderately simple, but with no annotations, no output schema, and only 50% schema description coverage, the definition leaves important gaps around return values and matching behavior. It is adequate for identifying the batch use case but not complete enough to fully predict results.

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 50%, and the description adds some meaning by noting that each item can carry its own state hint. However, it does not explain the top-level level parameter or clarify matching semantics beyond what the schema and property names already provide.

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 batch operation: matching up to 1,000 place names at once, with the spreadsheet-column example making the use case concrete. It is distinguishable from the singular sibling match_place_name by its explicit batch scope, though it does not name or directly contrast that sibling.

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 spreadsheet-column example implies when to use this tool, but there is no explicit guidance on when not to use it or when to choose match_place_name for a single lookup. Alternatives such as get_place or search_places are not discussed.

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.