Skip to main content
Glama

List UAE accredited e-invoicing providers

list_accredited_service_providers
Read-onlyIdempotent

Use this when the user asks which companies are accredited e-invoicing service providers (ASPs) in the UAE, whether a named company is accredited, or for the official ASP list. The UAE Ministry of Finance register of accredited e-invoicing service providers (ASPs): company names, accreditation numbers and websites as published, with the date the register was last updated, the date it was checked and the official link. The register grows as more providers are accredited, so point the user to the source page before they appoint one. Rows keep the register's order: it is not a ranking, and no provider is recommended. Pass search to look up one company by name. Do not use it to choose or rank a provider: it lists the register as published.

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": "list_accredited_service_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoPart of a company name, to check whether it is on the register.

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. Beyond that, the description discloses that rows preserve register order and are not a ranking, that no provider is recommended, that the register grows over time, and that results carry last-updated/checked dates and an official link — substantive behavioral context an agent needs to present results responsibly.

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?

Trigger conditions are front-loaded in the first sentence, with data-shape and caveats following. There is mild redundancy between 'it is not a ranking, and no provider is recommended' and the closing 'Do not use it to choose or rank a provider', but each sentence carries real guidance.

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?

There is no output schema, yet the description enumerates the returned fields (names, accreditation numbers, websites, update/checked dates, official link), the ordering semantics, and the volatility caveat. For a one-optional-parameter read tool, nothing an agent needs in order to call and present results 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 'search' parameter is already documented as a partial company name. The description's 'Pass search to look up one company by name' restates that intent without adding matching rules, case sensitivity, or empty-result behavior, so the schema does the heavy lifting.

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 states a specific verb and resource (list UAE Ministry of Finance accredited e-invoicing service providers) and enumerates the returned fields. No sibling tool covers this register, so the agent can route here without ambiguity.

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 explicit trigger conditions ('user asks which companies are accredited', 'whether a named company is accredited', 'for the official ASP list') and an explicit exclusion ('Do not use it to choose or rank a provider'). The alternative behavior — ranking or selecting a provider — is called out as out of scope.

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