Insurers Global

Resolve a former insurer name to today’s entity

resolve_former_name

Read-onlyIdempotent

Resolve a company name that is no longer in use to the insurer listed today. Use this when a policy, certificate or older document names an insurer that does not appear in search_insurers — the company may have been renamed, merged or delisted. Returns what happened, when, and the current entity where one exists. A renamed, acquired, merged or transferred insurer keeps its licence, so its policies continue with the successor; only "failed" means the company failed.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	The former company name, or part of it, as printed on the document.
`limit`	No	Maximum number of results to return.
`offset`	No	Results to skip, for paging.

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.

Changed2 schema fields changedSep 23, 2026

addedInput schema / properties / limit

Added value: +{
+  "default": 25,
+  "description": "Maximum number of results to return.",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

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

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 readOnly/idempotent/non-destructive, and the description adds value beyond that: it discloses that results include what happened, when, and the current entity where one exists, and it explains the licence/policy continuation semantics. This is useful behavioral context without contradicting any annotation.

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?

Four dense sentences each earn their place: the purpose, the trigger condition, the return shape, and the crucial failed-vs-successor nuance. No filler or repetition of schema details.

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?

With a full output schema, complete parameter documentation, and helpful annotations, the description covers the remaining context an agent needs: when to call it, what it returns, and how to interpret the outcome. Nothing essential 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 coverage is 100%, so the schema fully documents name, limit, and offset. The description reinforces that name is the former company name as printed on the document, but it does not add detail about paging or limits beyond what the schema already provides.

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 operation — resolving a defunct company name to the current insurer entity — and explicitly contrasts it with search_insurers, which covers names that do appear. This distinguishes the tool from siblings without opening schemas.

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?

It states the precise trigger: use when an older document names an insurer not found in search_insurers due to renaming, merger, or delisting. It also names the alternative (search_insurers) and clarifies that merged/acquired insurers retain their licence, with only 'failed' meaning the company failed.

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?