Skip to main content
Glama

Check who publishes a phone number in Ghana

contacts.check_number
Read-only

Use this when someone was given a phone number said to belong to a bank, mobile network or public office in Ghana and asks whether it is really theirs (for example "is 0800 422 422 really GCB"). It says which organisation on its list publishes that number on its own website, or that none does. A number that is not found may still be genuine, and the tool says so. Do not use it to look up who owns a private number, to trace a caller, or for numbers outside Ghana.

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

Input Schema

NameRequiredDescriptionDefault
numberYesThe phone number or short code as given, for example "0800 422 422", "+233 30 261 1611" or "292".

Output Schema

NameRequiredDescriptionDefault
foundYes
numberYes
cautionYes
read_onYes
explore_urlNo
published_byYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds a genuinely useful behavioral caveat beyond the annotations: a number that is not found may still be genuine, and the tool reports that rather than implying fraud. It says nothing about rate limits or lookup latency, which keeps it short of a 5.

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?

Front-loaded with the usage trigger, then the output behavior, then the negative space of exclusions — a natural decision order for an agent. Every sentence contributes either a trigger, a result semantic, or a boundary; none is filler.

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?

With one fully documented parameter, an output schema, and read-only annotations, the remaining burden is scope and result interpretation — both handled explicitly. An agent has everything needed to decide to call it and how to read a negative result.

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 'number' parameter already carries format examples and a maxLength, so the description does not need to explain it. The description adds only the contextual point that the number is 'as given', which is marginal beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: it reports which organisation on its list publishes a given phone number on its own website, or that none does. The Ghana scope and the publisher-list mechanism make it distinguishable from adjacent operations such as reverse owner lookup or call tracing.

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?

Gives an explicit trigger scenario ('someone was given a phone number said to belong to a bank, mobile network or public office in Ghana') with a concrete example query. It also names three exclusions — private-number ownership, caller tracing, and non-Ghana numbers — so the agent knows when to route elsewhere.

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