Skip to main content
Glama

regdata_nigeria_cac

Search the official Nigerian CAC registry by entity name or RC/BN/IT number. Get registration details, classification, business nature, and status, including verified not-found answers.

Instructions

Nigeria CAC Company Registry Scraper. Search the official Nigerian CAC register by entity name or RC/BN/IT number. Returns registered name, registration number, classification, nature of business and status for companies, business names and incorporated trustees. A verified "not found in the register" is a real answer. Advanced fields beyond this schema are also accepted (regdata_describe lists them).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxItemsNoOptional cap on billed dataset items returned.
companyNamesNoOne or more entity names to search, each looked up separately. Matching is the register's own name-similarity search, so partial names work: 'DANGOTE' returns every entity whose name contains it. Broad terms hit the register's 50-result ceiling - see Max results per query.
statusFilterNoKeep only entities in these registry statuses. Leave empty to export every match, which is the safer default for screening - an INACTIVE or DISSOLVED counterparty is usually the finding you most want to see, not one to filter away.
nameMatchModeNoHow closely an entity name must answer a name query. The register's search matches on single common words, so a search for a company that does NOT exist still returns a full page of unrelated entities - 'NOTAREALFIRM LIMITED' returns 49 results purely because they contain 'LIMITED'. 'Relevant' (default) drops rows that share nothing but boilerplate with your query. 'Strict' keeps only rows containing every identifying word. 'All' returns the register's raw output, including the noise. Registration-number lookups are exact and are never affected by this.relevant
maxResultsPerQueryNoMaximum records to export per query. The register itself returns at most 50 matches and provides no pagination, so 50 is the ceiling here too - a broader term cannot be paged through. To reach matches beyond the ceiling, narrow the name or search by registration number.
registrationNumbersNoOne or more registration numbers, each looked up separately. Accepts any format: 'RC 71242', 'RC-71242' or just '71242'. Include the prefix to restrict the classification - RC = company, BN = business name, IT = incorporated trustees. A bare number matches those digits across ALL THREE classifications, which is deliberate: the same digits genuinely exist as different entities (RC 71242 and IT 71242 are unrelated organisations).
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: name-similarity matching, partial name support, the register's 50-result ceiling, exact registration-number lookups, and the effect of nameMatchMode. It also explains that broad terms hit the ceiling and how to reach beyond it.

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 description is moderately long but well-organized with clear sentences. It could be slightly more concise, but the level of detail is justified given the tool's complexity. No wasted sentences.

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?

Given the lack of an output schema, the description covers the essential context: input methods, behavior, limitations (50-result ceiling), and the significance of 'not found'. It is comprehensive for a tool with multiple parameters and search modes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

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

Schema coverage is 100%, but the description adds significant value beyond the schema. For example, it explains how nameMatchMode affects results (including the 'LIMITED' example), why leaving statusFilter empty is safer for screening, and the format flexibility of registration numbers. This extra context aids correct parameter usage.

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 clearly identifies the tool as a scraper for the Nigerian CAC registry, specifies search by entity name or registration number, and lists the returned fields (registered name, registration number, etc.). It is distinct from sibling tools which target other registries.

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

Usage Guidelines4/5

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

The description explains when to use the tool (to search the Nigerian CAC register) and mentions advanced fields available via regdata_describe. It also clarifies that a 'not found' result is valid. However, it does not explicitly contrast with sibling tools or state when not to use it.

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