coverage-rights

list_insurers

Read-onlyIdempotent

List tracked U.S. health insurers with whether verified CMS-0057-F prior-authorization metrics are available for each.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_insurers"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`_note`	Yes
`insurers`	Yes
`_coverage`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedNov 10, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

changedOutput schema / properties / _coverage / properties / content_reviewed_at / anyOf

Previous value: -[
-  {
-    "format": "date",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "format": "date",
+    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / _coverage / properties / continuation / properties / url / $ref
```
Removed value: -"#/properties/_coverage/properties/sources/items/properties/url"
```
addedOutput schema / properties / _coverage / properties / continuation / properties / url / format
```
Added value: +"uri"
```
addedOutput schema / properties / _coverage / properties / continuation / properties / url / type
```
Added value: +"string"
```
changedOutput schema / properties / _coverage / properties / sources / items / additionalProperties
```
Previous value: -trueNew value: +{}
```
changedOutput schema / properties / insurers / items / additionalProperties
```
Previous value: -trueNew value: +{}
```
removedOutput schema / properties / insurers / items / properties / lines_of_business / $ref
```
Removed value: -"#/properties/_coverage/properties/limitations"
```
addedOutput schema / properties / insurers / items / properties / lines_of_business / items
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / insurers / items / properties / lines_of_business / type
```
Added value: +"array"
```

changedOutput schema / properties / insurers / items / properties / metrics_scope / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "lines_of_business": {
-        "$ref": "#/properties/_coverage/properties/limitations"
-      },
-      "reporting_cohort": {
-        "enum": [
-          "multi-line",
-          "medicare-advantage",
-          "marketplace"
-        ],
-        "type": "string"
-      },
-      "source_scope": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "reporting_cohort",
-      "lines_of_business",
-      "source_scope"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "lines_of_business": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "reporting_cohort": {
+        "enum": [
+          "multi-line",
+          "medicare-advantage",
+          "marketplace"
+        ],
+        "type": "string"
+      },
+      "source_scope": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "reporting_cohort",
+      "lines_of_business",
+      "source_scope"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed1 schema field changedNov 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "_coverage": {
+      "additionalProperties": false,
+      "properties": {
+        "applicability": {
+          "additionalProperties": false,
+          "properties": {
+            "jurisdiction": {
+              "type": "string"
+            },
+            "personal_deadline_calculated": {
+              "const": false,
+              "type": "boolean"
+            },
+            "scope": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "jurisdiction",
+            "scope",
+            "personal_deadline_calculated"
+          ],
+          "type": "object"
+        },
+        "content_reviewed_at": {
+          "anyOf": [
+            {
+              "format": "date",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "YYYY-MM-DD only when this specific content has an existing review date; null means no response-wide review date is asserted."
+        },
+        "continuation": {
+          "additionalProperties": false,
+          "properties": {
+            "label": {
+              "type": "string"
+            },
+            "url": {
+              "$ref": "#/properties/_coverage/properties/sources/items/properties/url"
+            }
+          },
+          "required": [
+            "label",
+            "url"
+          ],
+          "type": "object"
+        },
+        "limitations": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "schema_version": {
+          "const": "1.0",
+          "type": "string"
+        },
+        "sources": {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "label": {
+                "type": "string"
+              },
+              "role": {
+                "enum": [
+                  "primary_source",
+                  "publisher_data",
+                  "curated_guidance",
+                  "methodology"
+                ],
+                "type": "string"
+              },
+              "url": {
+                "format": "uri",
+                "type": "string"
+              }
+            },
+            "required": [
+              "label",
+              "url",
+              "role"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "status": {
+          "enum": [
+            "ok",
+            "no_matches",
+            "not_found",
+            "needs_context",
+            "unsupported"
+          ],
+          "type": "string"
+        },
+        "summary": {
+          "type": "string"
+        },
+        "tool": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "schema_version",
+        "tool",
+        "content_reviewed_at",
+        "status",
+        "summary",
+        "applicability",
+        "sources",
+        "continuation",
+        "limitations"
+      ],
+      "type": "object"
+    },
+    "_note": {
+      "type": "string"
+    },
+    "insurers": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "has_verified_metrics": {
+            "type": "boolean"
+          },
+          "lines_of_business": {
+            "$ref": "#/properties/_coverage/properties/limitations"
+          },
+          "metrics_scope": {
+            "anyOf": [
+              {
+                "additionalProperties": true,
+                "properties": {
+                  "lines_of_business": {
+                    "$ref": "#/properties/_coverage/properties/limitations"
+                  },
+                  "reporting_cohort": {
+                    "enum": [
+                      "multi-line",
+                      "medicare-advantage",
+                      "marketplace"
+                    ],
+                    "type": "string"
+                  },
+                  "source_scope": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "reporting_cohort",
+                  "lines_of_business",
+                  "source_scope"
+                ],
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "parent_org": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "slug": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "name",
+          "parent_org",
+          "lines_of_business",
+          "has_verified_metrics",
+          "metrics_scope"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "_note",
+    "_coverage",
+    "insurers"
+  ],
+  "type": "object"
+}

First observedJul 19, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add scope, which it does: only 'tracked' insurers are returned and each carries an availability flag for verified CMS-0057-F metrics. It doesn't mention ordering or pagination, but with an output schema present that is a minor gap.

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?

A single front-loaded sentence with no filler — the resource, the scope ('tracked'), and the per-item payload nuance are all packed in without redundancy.

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 parameters, rich annotations, and an output schema covering return values, the description supplies what an agent needs to select and call it. The only soft spot is the absence of explicit routing guidance to the metrics-fetching sibling, which is a usage concern rather than a completeness one.

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?

The tool takes zero parameters, so there is no parameter semantics to document; the baseline for a parameterless tool applies. Nothing in the schema needs compensating for in prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource ('List tracked U.S. health insurers') plus a distinguishing qualifier: it reports whether verified CMS-0057-F prior-authorization metrics exist per insurer. That clearly separates it from get_insurer_metrics, which presumably retrieves the metrics themselves, though no sibling is named explicitly.

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?

The definition implies a discovery/entry-point role — enumerate insurers and check metric availability before drilling in — but it never states when to use it versus get_insurer_metrics or rank_denial_rates, nor any exclusions. Usage is inferable rather than guided.

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

All coverage-rights 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?