Skip to main content
Glama

Check one agency's licence

verify_agency_licence
Read-only

Check the licence of ONE specific agency the user names (or its licence / facility number). Not for finding or listing agencies in a city or country - use search_agencies for that. Look up by agency name, or by licence / facility number (e.g. a UAE MOHRE facility number or Saudi Musaned reference). Returns the licence status recorded on GCC Domestic plus the official government registry link for independent verification.

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": {
      "name_or_licence": "<name_or_licence>"
    },
    "name": "verify_agency_licence"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoOptional country filter: uae | ksa | kuwait | qatar | bahrain | oman
name_or_licenceYesAgency name (English/Arabic) or licence/facility number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/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 the safety profile is covered. The description adds genuinely useful context beyond that: the lookup keys accepted (English/Arabic name, UAE MOHRE facility number, Saudi Musaned reference) and what the result contains (recorded licence status plus a government registry link). It does not address what happens if a name matches multiple agencies, which is a minor remaining gap.

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?

Three sentences, zero filler: scope constraint first, then the accepted lookup keys, then the return contents. Every sentence carries information an agent needs before calling.

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 no output schema, the description correctly compensates by stating what is returned (licence status plus official registry link). Annotations cover the safety profile. The only unaddressed case is ambiguous matches when looking up by agency name rather than by number.

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 100%, so the baseline is 3. The description goes beyond the schema by explaining that name_or_licence accepts Arabic or English names and by giving concrete registry-specific number examples (MOHRE facility number, Musaned reference), which materially helps the agent construct a correct value.

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 ("Check the licence of ONE specific agency") and immediately draws the boundary against the sibling that could be confused with it ("Not for finding or listing agencies... use search_agencies"). The agent can distinguish this from search_agencies without inspecting either schema.

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?

Explicit when-to-use (single named agency, lookup by name or licence/facility number) and explicit when-not-to-use (finding or listing agencies in a city or country), naming the alternative tool. Nothing is left to inference.

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.