insurance-mcp-poc
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | Yes | PostgreSQL connection string, e.g. postgres://insurance:insurance@localhost:55432/insurance | |
| EMBEDDING_DIM | No | Dimension of the embedding vectors, must match the vector(n) column in db/init.sql | |
| AZURE_OPENAI_KEY | No | Azure OpenAI API key, used only when replacing the default embedding model | |
| EMBEDDING_DEPLOYMENT | No | Azure OpenAI deployment name for the embedding model, used only when replacing the default embedding model | |
| AZURE_OPENAI_ENDPOINT | No | Azure OpenAI endpoint URL, used only when replacing the default embedding model |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_policy_documentsA | Semantic search over policy contracts, riders, underwriting guidelines and disclosure documents. Use this to answer questions about what a policy says. Returns ranked excerpts with document ids. |
| get_application_statusA | Look up a life insurance application by its number and return current status, the step it is waiting on, the assigned underwriter, and the full event timeline. |
| lookup_product_rulesA | Return a product’s issue limits and underwriting rules. When applicant_age, face_amount or state are supplied, also evaluates hard eligibility and flags which rules would trigger. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct aspect of insurance operations: policy document search, application status tracking, and product rule evaluation. There is no overlap in their purposes or outputs.
All tool names follow a consistent verb_noun pattern with snake_case: search_policy_documents, get_application_status, lookup_product_rules. The verbs (search, get, lookup) are semantically appropriate and uniform.
With only 3 tools, the server is tightly scoped to a specific insurance POC use case. Each tool addresses a core need without redundancy, making the count appropriate.
The main workflows of querying policy content, checking application status, and verifying product rules are covered. Minor gaps exist (e.g., no tools for creating/updating applications), but for a POC the surface is reasonably complete.