PolicyVera insurance quotes

Read a quote's PDF

get_quote_document

Read-only

Returns the carrier document an insurance agent attached to a quote, through PolicyVera's own download: the text PolicyVera reads out of a PDF, in the reply, and, when it fits, the file itself as a resource for apps that show files. requestId and quoteId come from check_quotes, which also lists each quote's documents; documentId picks one when a quote has more than one. A quote with no document answers that its fields are in check_quotes.

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": {
      "requestId": "<requestId>",
      "quoteId": "<quoteId>"
    },
    "name": "get_quote_document"
  }
}

Input Schema

Name	Required	Description
`quoteId`	Yes	The quote's id, from check_quotes.
`requestId`	Yes	The quote request's id, from check_quotes.
`documentId`	No	One of the quote's documents; omit when it has one.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 7, 2026
- addedInput schema / properties / quoteId / description
```
Added value: +"The quote's id, from check_quotes."
```
- addedInput schema / properties / requestId / description
```
Added value: +"The quote request's id, from check_quotes."
```
First observedNov 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, not open-world), so the description focuses on what the call actually yields: extracted PDF text in the reply plus the file as a resource "when it fits". The size-conditional file delivery is genuine context beyond the annotations, though truncation/size limits and permission assumptions are not spelled out.

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

Conciseness4/5

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

Nothing is wasted and the core return behavior is front-loaded, but the second sentence is a long comma-chained clause bundle that takes effort to parse. Tighter sentence breaks would improve scanability without losing content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must carry return semantics, and it does describe the text-in-reply plus optional resource shape. However, it omits what happens when extraction fails or the PDF is image-only, and gives no indication of size thresholds for the "when it fits" condition, which matters for a three-parameter read tool with no structured output.

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%, so every parameter is already documented, and the description mostly repeats the same provenance ("from check_quotes", "omit when it has one"). It adds only the mild linkage that both ids come from the same source and that documentId disambiguates multi-document quotes, which is already implied by the schema.

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?

States a specific verb and resource ("Returns the carrier document an insurance agent attached to a quote") and immediately scopes it against the sibling that lists documents (check_quotes) and the fallback case. An agent can distinguish it from check_quotes and read_policy_document without opening any schema.

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?

Explicitly routes the agent: get requestId/quoteId from check_quotes, use documentId when a quote has more than one document, and expect the answer "fields are in check_quotes" when no document exists. Prerequisite and alternative path are both named.

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?