Insurers Global

List licensed insurers with filters

list_insurers

Read-onlyIdempotent

List licensed insurers with optional filters and bounded pages (25 by default, at most 200; a page of large records stops early to keep the response small and reports nextOffset). Filter by continent ("africa", "europe", "asia-pacific", "south-america", "north-america"), country slug (e.g. "uganda"), class slug (e.g. "captive-risk-retention-group", "composite", "funeral-assistance", "general-non-life", "health-medical"), group type slug (e.g. "corporate-parent-captive", "domestic-private", "foreign-multinational", "mutual-cooperative"), parent group slug or verification level. Country filtering fetches only that market's full insurer records; compact returns lean rows instead.

Input Schema

TableJSON Schema

Name	Required	Description
`class`	No	Class of business slug.
`group`	No	Parent group slug, e.g. "allianz"; list_groups returns them all.
`limit`	No	Maximum number of results to return.
`offset`	No	Results to skip, for paging.
`compact`	No	true: return each insurer as a lean row (slug, name, country, class, groupSlug, verification) without notes, source text, identifiers or links, so more rows fit in one response. get_insurer returns the full record for any slug.
`country`	No	Country slug (e.g. "uganda") or ISO alpha-2 code (e.g. "UG").
`continent`	No	Continent slug.
`group_type`	No	Ownership group type slug.
`verification`	No	Verification level against the source register.

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No
`error`	No
`dataset`	No
`licence`	No
`version`	No	Dataset version the result was read from.
`verified`	No	Date the dataset snapshot was verified.
`retryable`	No
`verificationNote`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 23, 2026

addedInput schema / properties / compact

Added value: +{
+  "default": false,
+  "description": "true: return each insurer as a lean row (slug, name, country, class, groupSlug, verification) without notes, source text, identifiers or links, so more rows fit in one response. get_insurer returns the full record for any slug.",
+  "type": "boolean"
+}

Changed1 schema field changedSep 23, 2026

changedInput schema / properties / country / description

Previous value: -"Country slug (e.g. \"egypt\") or ISO alpha-2 code (e.g. \"EG\")."New value: +"Country slug (e.g. \"uganda\") or ISO alpha-2 code (e.g. \"UG\")."

Changed1 schema field changedSep 23, 2026

changedInput schema / properties / country / description

Previous value: -"Country slug (e.g. \"malaysia\") or ISO alpha-2 code (e.g. \"MY\")."New value: +"Country slug (e.g. \"egypt\") or ISO alpha-2 code (e.g. \"EG\")."

Changed2 schema fields changedSep 17, 2026

changedInput schema / properties / country / description

Previous value: -"Country slug (e.g. \"ghana\", \"france\") or ISO alpha-2 code (e.g. \"GH\", \"FR\")."New value: +"Country slug (e.g. \"malaysia\") or ISO alpha-2 code (e.g. \"MY\")."

changedInput schema / properties / group / description

Previous value: -"Parent group slug, e.g. \"sanlam-allianz\" or \"allianz\"."New value: +"Parent group slug, e.g. \"allianz\"; list_groups returns them all."

First observedSep 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond annotations: bounded pages, early stopping for large records, nextOffset reporting, and the country-filter behavior of fetching full insurer records. It doesn't detail the output schema, but an output schema exists, so that burden is already met.

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 dense but well-organized: it front-loads the core action and pagination, then lists filters with examples, and ends with the compact-mode clarification. Every sentence earns its place, though the filter list is long and could arguably be trimmed since the schema already enumerates the enums.

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?

For a read-only list tool with 9 optional parameters, an output schema, and full schema coverage, the description covers the key operational details: pagination bounds, early-stop behavior, filter examples, and the compact/full distinction. It doesn't explain the default sort order or how to combine filters, but those are minor gaps given the output schema and annotations.

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 description coverage is 100%, so the baseline is 3. The description adds value by giving concrete example values for country ('uganda'), class ('captive-risk-retention-group'), group_type ('corporate-parent-captive'), and by explaining the compact parameter's effect on row shape. It also clarifies the country filter's side effect (fetching full records). This goes beyond the schema's terse descriptions.

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 opens with a specific verb ('List') and resource ('licensed insurers'), then immediately names the optional filters and pagination behavior. It clearly distinguishes this tool from siblings like get_insurer (full record for a slug) and search_insurers (search), and the compact-mode note explicitly contrasts with get_insurer.

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?

The description gives explicit filter values and examples, states the default and maximum page size, and explains when compact mode is useful ('so more rows fit in one response'). It also points to get_insurer for full records and list_groups for parent group slugs, giving the agent clear routing guidance.

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

All Insurers Global tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?