Skip to main content
Glama

list_contact_states

Read-only

List exact ConnectReseller state names for a country name, country ID, or ISO code. Use the returned name in contact requests.

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

Input Schema

NameRequiredDescriptionDefault
countryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a safe, closed-world read, so the description does not need to repeat that. It does add real behavioral value by stressing 'exact' state names and the intended consumption of the values, implying the returned strings must be passed through verbatim rather than normalized by the caller.

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 short sentences with zero filler: the first defines the operation and its inputs, the second states how to use the result. The purpose is front-loaded and nothing is 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?

With one parameter, an output schema covering return values, and safety already encoded in annotations, the description covers nearly everything needed to call it. The only omission is error behavior for an unrecognized country, which is a minor gap for a simple lookup tool.

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

Parameters4/5

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

Schema description coverage is 0% for the single 'country' parameter, so the description must carry the semantics — and it does, enumerating three accepted forms (country name, country ID, ISO code). That is the key information an agent needs to format the call correctly.

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 opens with a clear verb and resource ('List exact ConnectReseller state names') and names the accepted lookup keys (country name, country ID, ISO code). It does not explicitly distinguish itself from the sibling list_contact_countries, but the resource is specific enough that an agent can tell the two apart by payload.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use the returned name in contact requests' gives concrete downstream context for when this tool is needed — specifically to obtain a valid state value before submitting contact data. It stops short of naming an alternative or stating when not to call it, which keeps it out of the 5 tier.

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.