Insurers Global

Get one insurance group

get_group

Read-onlyIdempotent

Get one insurance group by slug: home market, type, continents and countries covered, the slug of every licensed entity in the directory, and their records in insurersDetail. A large group returns a first page of records; insurersDetailPage gives the total and the nextOffset to pass as offset.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes	Group slug, e.g. "allianz".
`limit`	No	Maximum entity rows to return. Long lists also stop early to keep the response small; the page object reports total and nextOffset.
`offset`	No	Entity rows 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.

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.

Changed3 schema fields 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"
+}

addedInput schema / properties / limit

Added value: +{
+  "default": 200,
+  "description": "Maximum entity rows to return. Long lists also stop early to keep the response small; the page object reports total and nextOffset.",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Entity rows to skip, for paging.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

Changed1 schema field changedSep 17, 2026

changedInput schema / properties / slug / description

Previous value: -"Group slug, e.g. \"old-mutual-ltd\"."New value: +"Group slug, e.g. \"allianz\"."

First observedSep 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds meaningful behavioral context beyond annotations: pagination behavior for large groups, the insurersDetailPage total, and the nextOffset usage for paging. This gives an agent a realistic picture of response size and iteration without contradicting 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 two efficient sentences with zero filler. The primary purpose and return contents are front-loaded, and the pagination caveat is placed afterward without disrupting the core message.

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 read-only lookup tool with an output schema, the description covers the resource identity, return content, pagination, and compaction behavior. Nothing an agent needs to decide whether to call this tool or to understand its high-level output is missing.

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%, and each parameter already has a clear description with defaults and constraints. The tool description adds some context around offset paging and compact rows, but it mostly restates or complements what the schema already explains, so the baseline of 3 is appropriate.

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 names a specific verb and resource ('Get one insurance group by slug') and enumerates exactly what it returns: home market, type, geographic coverage, licensed entity slugs, and their insurersDetail records. This clearly distinguishes it from list_groups and 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 Guidelines4/5

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

The description implies usage for fetching a single group's aggregate data by slug, and the compact parameter explicitly points to get_insurer as the alternative for full insurer records. It does not explicitly name list_groups as the alternative for enumerating groups, so exclusions are only partially stated.

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?