ranked

List a regulator's register, as accessed

ranked_by_regulator

Read-onlyIdempotent

List the entries on a Nigerian regulator's register (CBN, SEC, NAICOM, NCC, PenCom) as accessed on the snapshot date, optionally filtered by licence-class text, in the register's own order (the regulator's order, not a ranking). Source is the regulator's own publication; the licence class is as the regulator states it. Each row carries the register's statement, hub_url, feed_url and place_url where Ranked has a matching listing. A register row is what the regulator's register listed on the access date. It is not a licence finding by Ranked, registers lag revocations, and absence from Ranked's copy is not proof that a name is unlicensed.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`offset`	No
`category`	No	filter on licence class / scope text, e.g. 'microfinance', 'broker', 'ISP', 'PFA'
`regulator`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already mark it read-only, idempotent, and non-destructive. The description adds useful transparency about snapshot-date access, the regulator's own ordering, returned URLs, and explicitly clarifies that this is not a Ranked licence finding.

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 structured and mostly efficient, but the final disclaimer about not being a licence finding is repeated with similar wording earlier. Still, it remains readable and front-loads the core action and scope.

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 helpfully states that each row includes the register's statement, hub_url, feed_url, and place_url where applicable. It also defines what a register row is. Minor gaps remain around response shape and pagination details, but the core context is covered.

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?

Only the 'category' parameter is described in the schema; 'regulator' has an enum but no explanatory text, and 'limit'/'offset' are left implicit. With 25% schema coverage, the description partially compensates by explaining the category filter but leaves standard pagination and regulator semantics underspecified.

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?

Clearly states the verb 'List' and the resource 'entries on a Nigerian regulator's register', with the regulator and optional licence-class filter. It also distinguishes itself from a ranking by noting the register's own order, separating it from ranking tools.

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?

Explains optional filtering and the source/order semantics, but does not explicitly say when to prefer this tool over siblings such as ranked_check_licence or ranked_rankings. The guidance is implicit rather than a direct comparison.

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

All ranked tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation5/5

Each tool targets a distinct query type: bulk regulator lists, single-name licence checks, single-product payment eligibility, multi-product comparison, dataset search, place details, rankings, hub browsing, and stats. Descriptions explicitly cross-reference the related tools (e.g., find_business directs users to rankings/place), so an agent should not confuse them.

Naming Consistency4/5

All tool names share the consistent ranked_ prefix and snake_case style, which is predictable. However, the suffix mixes clean verb-object forms (check_licence, find_business, compare) with other patterns (by_regulator, can_nigerian_pay, place, rankings, hubs), so it is not a uniform verb_noun convention.

Tool Count5/5

Nine tools is well within the ideal range for a read-only Nigerian business/regulator data server. Each tool earns its place by covering a distinct query workflow: register lookups, licence checks, payment eligibility, comparison, search, place details, rankings, hub navigation, and dataset stats.

Completeness4/5

The surface covers the core domain thoroughly: bulk regulator access, name-based licence checking, product usability, place details, rankings, search, and provenance stats. Minor gaps remain, such as no explicit state-level ranking endpoint and limited ability to list every place in a category beyond the top-25 published ranking, but there are no obvious dead ends.

Resources

Need Help?