Skip to main content
Glama

Organisations in Ghana whose contacts are listed

contacts.list
Read-only

Use this when someone asks which organisations this tool has numbers for, or wants the emergency numbers or the places to report fraud in Ghana all at once. Do not use it when one organisation is named: use contacts.find.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "contacts.list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOne group: emergency, regulator, network, bank, payments, utility, public_service. Leave out for the names of all.

Output Schema

NameRequiredDescriptionDefault
groupsYes
cautionYes
read_onYes
explore_urlNo
not_publishedNo
organisationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotations already establish read-only, non-destructive, closed-world behavior. The description adds useful domain context about Ghana organisations and contact numbers, but it does not add operational details such as pagination or filtering behavior; with an output schema present, this is adequate but not rich.

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 tight sentences are front-loaded with the usage condition and then the exclusion/alternative. There is no redundant or filler text.

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 read-only list tool with an output schema, the description gives sufficient selection guidance and domain scope. It could mention the optional kind filter, but the schema and output schema already carry that detail.

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 single optional kind enum is fully documented in the schema. The description does not explain the kind groups or how filtering interacts with the 'all at once' behavior, so it adds no meaning beyond the schema; baseline 3 applies.

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 conveys that the tool returns organisations in Ghana for which contact numbers exist, including emergency and fraud-reporting contacts en masse. It does not use a crisp 'List...' verb and is somewhat self-referential ('this tool has numbers for'), but the scope is distinguishable from contacts.find.

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

Usage Guidelines5/5

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

It explicitly states when to use the tool (asking which organisations have numbers, or needing emergency/fraud contacts all at once) and when not to use it (when one organisation is named), directing that case to contacts.find.

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.

Resources