Tools reference
The connector exposes fourteen read tools and two write tools. Every claim-scoped tool requires a claimId argument; search_claims is how an assistant resolves a name to that id in the first place. Read tools require claim:read; write tools also require claim:write.
These tools query the claim file. They do not mutate state, do not send communications, and do not return source data outside the authenticated user's tenant. All require claim:read.
search_claims
claim:readSearch the workspace for claims by insured name, address, claim number, or carrier. Returns up to 15 matches with id, insured, carrier, status, and days open.
Example user prompt
Find the Reyes hail claim from last summer.
get_claim_snapshot
claim:readFetch the structured snapshot for a claim: facts, parties, carrier, status, days open, open-task and excerpt counts. Use to anchor any follow-up question on the file.
Example user prompt
Give me the current state of the Reyes claim.
get_claim_timeline
claim:readRead the chronological timeline: communications, work events, status changes, carrier correspondence, photos, and files. Returns up to 40 most-recent entries.
Example user prompt
What's happened on the Reyes claim in the last two weeks?
get_claim_tasks
claim:readList work tasks on a claim with assignee, due date, and status. Filter by open or all.
Example user prompt
What's still open on the Reyes file?
get_policy_excerpts
claim:readReturn the operator-approved policy excerpts for a claim. Returns nothing if no excerpts have been approved in Coverage; the connector will not invent or infer policy language.
Example user prompt
What does the policy say about wind on the Reyes claim?
get_claim_weather_report
claim:readRead the federal weather report for the loss date and address: hail size, wind speed, storm classification, sources, and confidence.
Example user prompt
What was the weather on the date of loss for the Reyes property?
search_claim_evidence
claim:readSearch indexed claim files (estimates, invoices, letters, reports, photos with AI summaries) and return bounded citation summaries with citationIds.
Example user prompt
Find the carrier's last estimate on the Reyes claim.
get_evidence_chunk
claim:readFetch the source text for a citation returned by search_claim_evidence. Bounded to roughly 5,000 characters so a long document can be read incrementally.
Example user prompt
Show me the exact line item the carrier disputed.
get_estimate_variance
claim:readRead the existing estimate workbench comparison: carrier, public adjuster, and contractor estimates side by side, with RCV, ACV, depreciation, deductible, and scope summaries.
Example user prompt
Where do the carrier and contractor estimates differ on the Reyes claim?
get_claim_participants
claim:readList the people and organizations on a claim: insured, carrier, adjuster, contractor, public adjuster, attorney, and others, with email, phone, and last touchpoint.
Example user prompt
Who's the desk adjuster on the Reyes claim and when did we last hear from them?
get_claim_communications
claim:readRead recent claim communications: latest inbound and outbound, gaps, review state, recoverable drafts, and bounded recent email/call/SMS events.
Example user prompt
When did the carrier last reply on the Reyes claim?
get_claim_readiness
claim:readRead claim readiness: which inputs are missing for the next operator move (position package, e-sign, invoice, weather and code prerequisites, task-eligible gaps).
Example user prompt
What's blocking us from sending the Reyes package?
get_carrier_package_readiness
claim:readRead whether a claim is ready for a carrier package and what supporting inputs are missing. Read-only; never builds or sends anything.
Example user prompt
Are we ready to send the carrier package on the Reyes claim?
get_file_workspace_summary
claim:readRead the file workspace inventory and processing state: counts, indexing and search coverage, extraction trust, and file review queue. Pair with search_claim_evidence for source text.
Example user prompt
What's in the file workspace on the Reyes claim and what still needs review?
Write tools append to the claim record. They require both claim:read and claim:write. Both write tools are append-only: log_task creates a new task, log_note appends a timeline entry. Neither edits or deletes existing records.
Write actions are attributed to the connector and recorded in the audit trail with the user, the client id of the assistant that called them, and a timestamp. The operator can edit or close any connector-created task in the normal claim UI.
log_task
claim:writeCreate a new work task on a claim. Title, description, priority, and due date. Attributed to the connector; the operator can edit or close it normally.
Example user prompt
Add a task to call the adjuster about the deductible by Friday.
log_note
claim:writeAppend a timeline entry: a note, phone call summary, email record, meeting note, or letter sent. Records that something happened. Does not send or schedule anything.
Example user prompt
Log that the desk adjuster called and asked for a recorded statement.
The connector speaks JSON-RPC 2.0 over the Model Context Protocol on the /api/mcp endpoint. Most readers will never see the wire format directly; the AI assistant's MCP client handles it. For integrators building custom MCP clients:
POST /api/mcp HTTP/1.1
Authorization: Bearer <access_token>
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_claim_snapshot",
"arguments": { "claimId": "abc123" }
}
}The server implements initialize, tools/list, tools/call, and standard MCP notifications. Errors follow JSON-RPC error codes; missing or insufficient scope returns an insufficient_scope body matching RFC 6750.
See Auth and security for the OAuth metadata document URL.