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. "micronesia"), 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. "micronesia") or ISO alpha-2 code (e.g. "FM").
`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 27, 2026

changedInput schema / properties / country / description

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

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 genuine behavioral insight beyond annotations: pages stop early for large records, nextOffset is reported, and country filtering returns full records while compact returns lean rows. This is valuable context not visible in the schema or annotations.

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?

The description is dense but every sentence earns its place. It front-loads the core behavior in the first sentence, then packs filter guidance and response-shaping caveats into the following two sentences with no filler or repeated schema content.

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 9-parameter list tool with no required parameters and an output schema present, the description is complete: it covers all filter families, pagination behavior, response-size handling, and the compact-mode alternative. The output schema covers return structure, so the description does not need to restate it. Nothing an agent needs to call this tool correctly is missing.

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 flexibly, but the description adds meaning beyond the schema: it explains pagination defaults and bounds, gives concrete slug examples for class and group type, and clarifies the semantic difference between compact and full record returns. The parameter guidance is therefore above baseline without being redundant.

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 clear verb and resource: 'List licensed insurers with optional filters and bounded pages.' It immediately distinguishes the tool from single-record or search siblings by stating it lists insurers and supports filters. The pagination and compact-mode details further sharpen what this specific tool does.

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 gives clear context for when to use filters and compact mode, and references alternatives in the schema ('get_insurer returns the full record for any slug', 'list_groups returns them all'). It does not explicitly draw a when-not contrast with search_insurers, but the context is strong enough for an agent to route correctly.

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?