Skip to main content
Glama

regdata_uae_adgm_public_register

Find UAE ADGM company details by name, identifier, or trade name. Retrieve registration number, status, type, incorporation date, address, and trade names from the public register.

Instructions

UAE ADGM Public Register Scraper - Company Data. Scrape the Abu Dhabi Global Market (ADGM) public register: company name, registration number, status, type, classification, incorporation date, address and trade names. Search by name, identifier or trade name. No API key. Advanced fields beyond this schema are also accepted (regdata_describe lists them).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxItemsNoOptional cap on billed dataset items returned.
pageSizeNoHow many results to fetch per request (1-100). Larger pages are faster; the default is fine for most runs.
minIntervalMsNoPolite delay between requests to the register. 350ms is a safe default.
searchQueriesYesEntity names, registration numbers or trade names to search the ADGM public register for. Each query returns all matching entities (paginated up to the limit below).
maxResultsPerQueryNoMaximum number of entities to extract per search query. 0 means no limit (fetch all matches).
Behavior3/5

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

No annotations provided, so description bears full burden. 'Scrape' implies read-only, but does not explicitly state non-destructive behavior, rate limits, or error handling. Acceptable but minimal disclosure.

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, no fluff. Front-loaded with purpose and scope. Every sentence adds value. Excellent conciseness.

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?

No output schema, but description lists returned fields and search methods. Mentions regdata_describe for deeper schema. Covers key aspects for a scraper tool. Could add notes on data freshness or pagination behavior, but overall sufficient.

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 description coverage is 100%, baseline 3. Description adds value by stating search by name/identifier/trade name, but this mostly mirrors schema. Cross-reference to regdata_describe for advanced fields is helpful but minor.

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?

Description clearly states verb 'Scrape', specific resource 'UAE ADGM public register', and lists fields (company name, registration number, etc.). Name and context distinguish it from sibling tools covering other countries/registers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage for ADGM register, but no explicit when/when-not guidance. Mentions 'No API key' as prerequisite and cross-references regdata_describe for advanced fields, but does not clarify when to use this tool over other regdata_* tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nolpak14/getregdata'

If you have feedback or need assistance with the MCP directory API, please join our Discord server