Skip to main content
Glama

insurepulse

Assess insurance needs across auto, life, home, renters, and business. Find coverage gaps, review policies, and optimize rates with AI.

Instructions

InsurePulse: AI-synthesized insurance intelligence. Auto coverage analysis, life insurance needs calculator, homeowners gap finder, annual coverage audit, and renters insurance guidance. All endpoints require x402

Coverage: Global

Endpoints: • auto ($0.10): Auto insurance analysis • life ($0.10): Life insurance needs calculator • home ($0.10): Homeowners insurance gap analysis • review ($0.15): Annual insurance coverage review • renters ($0.08): Renters insurance guide • business ($0.10): Business insurance guidance • claim ($0.08): Insurance claims guidance • disability ($0.10): Disability insurance analysis • life-event ($0.10): Life-event insurance checklist • rate ($0.08): Insurance rate optimizer • umbrella ($0.08): Umbrella insurance analysis

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageNoApplicant age
dogNoWhether tenant has a dog (affects liability)
zipNoZIP code for rate context
debtNoOther debt (student loans, auto, credit card) in USD
langNoResponse language
sqftNoSquare footage
eventNoLife event (marriage, baby, home-purchase, divorce)
stateNoState of registration (e.g. 'Texas', 'CA')
valueNoHome value or purchase price in USD
actionYesWhich endpoint to call. Options: auto | life | home | review | renters | business | claim | disability | life-event | rate | umbrella
incomeNoAnnual gross income in USD
countryNoISO country code (e.g. US, UK, DE, CA, AU) — tailors norms and benchmark anchors. Default US.
detailsNoAdditional context
profileNoDriver profile description (e.g. 'clean record 10 years, married, homeowner')
revenueNoAnnual revenue USD
vehicleNoVehicle description (e.g. '2020 Toyota Camry')
locationNoCity and state (e.g. 'Austin TX')
mortgageNoRemaining mortgage balance in USD
policiesNoCurrent policies held (e.g. 'auto,home,life,umbrella')
employeesNoEmployee count
net_worthNoEstimated net worth (in local currency) for umbrella/liability sizing
owns_homeNoOwns home (yes/no)
situationNoLife situation description (e.g. 'married, 2 kids, dual income')
deductibleNoPolicy deductible USD
dependentsNoNumber of financial dependents
life_stageNoRecent life events (e.g. 'new baby', 'home purchase', 'retirement')
occupationNoOccupation
employer_ltdNoExisting employer long-term disability (yes/no/details)
teen_driversNoTeen drivers (yes/no)
business_typeNoBusiness type (e.g. consulting, retail, contractor)
insurance_typeNoInsurance type (auto, home, renters)
current_premiumNoCurrent premium USD
damage_estimateNoEstimated damage USD
rental_propertyNoOwns rental property (yes/no)
current_coverageNoCurrent dwelling coverage amount in USD
Behavior2/5

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

No annotations are provided. The description does not disclose behavioral traits beyond listing endpoints and pricing. It mentions 'All endpoints require x402' but does not explain what that means (authentication key). No information on side effects, rate limits, response format, or data handling.

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?

The description is moderately concise, starting with a clear purpose statement. The endpoint list is structured in bullet points with pricing, but some repetition (e.g., 'Auto insurance analysis' and 'auto ($0.10): Auto insurance analysis'). The 'x402' requirement is important but not explained.

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

Completeness2/5

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

Given 35 parameters and 11 endpoints, the description does not map which parameters apply to which endpoint. No output schema is present, and the description does not explain return values or response structure. The tool is complex, but the description provides only a high-level endpoint list.

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?

The input schema has 100% description coverage for all 35 parameters, each with clear descriptions. The tool description does not add additional meaning beyond the schema. Since schema already documents parameters, the description adds no extra value.

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 description clearly states 'AI-synthesized insurance intelligence' and lists 11 specific endpoints with their purposes (e.g., 'Auto insurance analysis'). The name 'insurepulse' aligns with insurance domain, distinguishing it from sibling tools like 'alphapulse' or 'arbipulse' which cover other domains.

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 description implies the tool is for insurance-related queries by listing endpoints, but does not explicitly state when to use this tool over others. No 'when not to use' guidance or alternatives are provided. Usage context is implicit through the endpoint list.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GTCC777/mcp-pulsenetwork'

If you have feedback or need assistance with the MCP directory API, please join our Discord server