PolicyVera insurance quotes

Licensed insurance agents for your state and coverage

list_agents

Read-only

Lists licensed insurance agents who quote at least one of the coverage types in the person's state, in PolicyVera's own order, not a ranking, each with their agency, their license number for the person's state (license), their National Producer Number, or NPN (npn), and the languages they speak besides English (speaks). With the person's ZIP each insurance agent carries its distance; nearestFirst is PolicyVera's own nearest-first order. The list comes a page at a time (page, pages and total in the reply). Google's rating and review count are not in the list. The list can be sorted or filtered on distance, the states an insurance agent is licensed in, and time to first quote. When the person asked for several coverage types, each insurance agent carries quotesOfYourLines and, when they do not quote them all, lineGap: PolicyVera's own sentence for it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lines": "<lines>"
    },
    "name": "list_agents"
  }
}

Input Schema

Name	Required	Description
`zip`	No	The person's ZIP, when they gave it: each insurance agent then carries its distance, and the list can be nearest first.
`page`	No
`lines`	Yes
`state`	No	The state of the home being insured (or where the vehicle is garaged). Leave it out to use the state where PolicyVera has the person living; give the home's state when the home is elsewhere.
`nearestFirst`	No	true when the person asks for the closest insurance agents: PolicyVera's own nearest-first order.
`zipConfirmed`	No	Only after this door asked about the ZIP and the person said it is right.

Output Schema

Name	Required	Description	Default
`next`	No
`page`	No
`said`	No
`basis`	No
`order`	No
`pages`	No
`state`	No
`total`	Yes
`agents`	Yes
`groups`	No
`linesNote`	No
`stateFrom`	No
`groupsNote`	No
`locationNote`	No
`measuredFrom`	No
`locationRequired`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 7, 2026

removedOutput schema / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / agents / items / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / agents / items / properties / license / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "number": {
-        "type": "string"
-      },
-      "state": {
-        "type": "string"
-      },
-      "verified": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "state",
-      "number",
-      "verified"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "number": {
+        "type": "string"
+      },
+      "state": {
+        "type": "string"
+      },
+      "verified": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "state",
+      "number",
+      "verified"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / groups / additionalProperties
```
Removed value: -false
```

First observedNov 4, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds genuinely new behavior: results come back paginated (page/pages/total), ordering is PolicyVera's internal order and explicitly not a ranking, distance is attached only when ZIP is supplied, and quotesOfYourLines/lineGap vary with the number of requested lines. It stops short of naming failure modes or limits beyond what the schema lists (page max 50).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Content is dense and mostly earns its place, but the opening sentence runs past ninety words and bundles return fields, filters, and ordering into one clause chain. Ordering semantics are stated twice ("in PolicyVera's own order, not a ranking" and again for nearestFirst), which is avoidable repetition.

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 listing tool with an output schema and full annotation coverage, the definition supplies enough to call it correctly: required filter, optional scoping by state and ZIP, ordering, and pagination. Minor gaps remain around the zipConfirmed gate and the meaning of page bounds, but they do not block correct invocation.

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?

With 67% schema coverage the description still adds real meaning: zip drives per-agent distance and enables nearest-first ordering, nearestFirst is defined as PolicyVera's own proximity order, and lines is tied to quotesOfYourLines/lineGap. It does not explain page (beyond noting pagination) or the zipConfirmed confirmation gate, which is the most consequential unexplained parameter.

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 first sentence states a specific verb and resource ("Lists licensed insurance agents") plus the exact filter (agents who quote at least one of the requested coverage types in the person's state). It also carves out scope negatively ("Google's rating and review count are not in the list"), which implicitly separates it from review-oriented siblings.

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?

It gives conditional guidance inside the call ("When the person asked for several coverage types...", "With the person's ZIP each insurance agent carries its distance"), so usage context is implied. But it never states when to choose this tool over an alternative, nor any prerequisite such as obtaining the state/ZIP first from another tool.

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

All PolicyVera insurance quotes 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?