Skip to main content
Glama

Contact numbers of an organisation in Ghana

contacts.find
Read-only

Use this when someone asks for the customer-care, complaints or emergency number of a bank, mobile network, electricity company, payments company or public office in Ghana (for example "what is the GCB customer care number" or "how do I reach the passport office"). It returns numbers read on the organisation's own website, with the page and the date. Give those numbers rather than one from memory or from a web search. Do not use it for a shop, a school, a hospital, a person, or an organisation outside Ghana: it covers a fixed list and says when a name is not on it.

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": {
      "organisation": "<organisation>"
    },
    "name": "contacts.find"
  }
}

Input Schema

NameRequiredDescriptionDefault
organisationYesThe organisation's name or usual short name, for example "GCB", "MTN", "ECG", "passport office" or "police".

Output Schema

NameRequiredDescriptionDefault
cautionYes
read_onYes
explore_urlNo
not_publishedNo
organisationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (read-only, closed-world, non-destructive), the description discloses provenance ('numbers read on the organisation's own website, with the page and the date') and miss behavior ('says when a name is not on it'). The closedWorldHint=false in annotations is corroborated by the explicit 'fixed list' and 'organisation outside Ghana' boundary statements.

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?

The trigger condition is front-loaded in the first clause, followed by examples, a routing preference, and exclusions. Every sentence carries a distinct piece of information: scope, evidence source, alternative behavior, and boundaries.

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

Completeness5/5

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

For a single-parameter read-only lookup with an output schema and full annotation coverage, the description closes the remaining gaps: who it covers, who it excludes, where the data comes from, and what happens on a miss. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100% and the single 'organisation' parameter is already documented with examples, so the schema does most of the work. The description nonetheless adds real meaning by saying the lookup operates over a fixed list of organisations and that the tool reports when a name is not on it, which tells the agent how to phrase the argument and what a miss looks like.

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 concrete verb and resource (returns customer-care/complaints/emergency numbers for named organisations in Ghana) and even illustrates typical requests. It does not name or distinguish itself from the siblings contacts.check_number or contacts.list, so an agent must infer the boundary from scope alone rather than from explicit routing.

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 states when to use (bank, mobile network, electricity, payments, public office in Ghana), gives example queries, and explicitly excludes shops, schools, hospitals, persons and non-Ghanaian organisations. It also ranks itself against an alternative ('give those numbers rather than one from memory or from a web search'), which is exactly the priority guidance an agent needs.

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