Skip to main content
Glama

Check a UAE TRN

check_trn
Read-onlyIdempotent

Use this when the user asks whether a UAE TRN (tax registration number) looks valid or whether a business is registered for UAE e-invoicing on Peppol ("is TRN 100… valid?"). Checks that a UAE Tax Registration Number has the right format (15 digits; spaces and dashes are fine) and looks it up in the public Peppol Directory to see whether the business is registered for UAE e-invoicing. A valid format does not prove the TRN exists or is active: for that the user opens the TRN checker (link in the result), which asks the FTA register after the user types the FTA's security code. Do not use it to prove a TRN is active with the FTA: the result links the TRN checker, where the user sees the FTA register's answer.

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": {
      "trn": "<trn>"
    },
    "name": "check_trn"
  }
}

Input Schema

NameRequiredDescriptionDefault
trnYesThe TRN as the user wrote it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, it discloses the actual mechanics: format validation, a lookup against the public Peppol Directory, and the important limitation that a valid format does not prove the TRN exists or is active. It also explains that the FTA confirmation requires the user to type a security code in the linked checker, which is non-obvious behavior an agent could otherwise misreport.

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?

The trigger and core behavior are front-loaded in the first two sentences. The closing sentence partly repeats the earlier 'a valid format does not prove the TRN exists' point, so there is mild redundancy, but nothing is padding or off-topic.

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 tool with no output schema, the description covers what is checked, what the result contains (a link to the TRN checker), and the boundary of what the answer proves. An agent has everything needed to call it and to frame the result honestly.

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%, so the baseline is 3, but the description adds real meaning beyond the schema's 'The TRN as the user wrote it' by specifying the expected format (15 digits, spaces and dashes tolerated). That tells the agent it need not normalize input before calling, which the schema alone does not convey.

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 ('Checks that a UAE Tax Registration Number has the right format') plus the second operation ('looks it up in the public Peppol Directory'). It also quotes a representative user question, making it immediately distinguishable from siblings like check_vat_registration or check_einvoicing_readiness.

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 ('Use this when the user asks whether a UAE TRN ... looks valid') and an explicit exclusion with the correct alternative ('Do not use it to prove a TRN is active with the FTA: the result links the TRN checker'). Both the when and the when-not are stated, along with where the user should go instead.

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