Skip to main content
Glama

Ghana Gov Guide

Check a web address against Ghana agencies' own

ghana_gov.check_website
Read-only

Use this when someone has a web address for a Ghana government service (a link in a message, a site that asks for payment, a "portal" for the Ghana Card, a licence, a passport, NHIS or a TIN) and asks whether it belongs to the agency. It says whether the address is one an agency on its list gives on its own pages, is under that agency's own domain, or is neither, and points out an address built to look like an agency's without being under it. It never says a site is safe. Do not use it for addresses outside Ghana's public services, or to open or test a site: it reads nothing from the address given.

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": {
      "address": "<address>"
    },
    "name": "ghana_gov.check_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe web address as given, for example "https://nia.gov.gh/faqs/", "dvla.gov.gh" or "nia-ghanacard-portal.com".

Output Schema

NameRequiredDescriptionDefault
hostYes
underNo
agencyNo
cautionYes
read_onYes
verdictYes
uses_nameNo
looks_likeNo
explore_urlNo
other_alphabetNo
text_before_atNo

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?

Annotations already declare readOnly and non-destructive, and the description adds substantive behavior the annotations cannot: a three-way classification of the address, detection of look-alike addresses, the explicit disclaimer that it never certifies a site as safe, and the note that it reads nothing from the address. That last point rules out any assumption that the tool fetches or scans the site.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the trigger before the exclusions, and no filler. The middle clause enumerating return states is slightly dense but each part earns its place.

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?

Output schema exists, yet the description still previews the outcome categories and the safety disclaimer, so an agent knows what a positive versus negative answer means. For a single-parameter read-only lookup, nothing needed 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.

Parameters3/5

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

Schema coverage is 100% and the single parameter already documents accepted forms with examples, so the schema carries the weight. The description only reinforces 'the web address as given' and that nothing is read from it; it adds little parameter-level meaning beyond the structured field.

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?

The description names a specific verb and resource: it decides whether a web address is one an agency publishes itself, sits under that agency's own domain, or is neither. It also lists the concrete service categories involved (Ghana Card, licence, passport, NHIS, TIN), which makes it instantly distinguishable from how_to and list_services.

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 gives an explicit trigger ('when someone has a web address ... and asks whether it belongs to the agency') and explicit exclusions ('Do not use it for addresses outside Ghana's public services, or to open or test a site'). The scope boundary is unambiguous without needing sibling comparison.

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