Skip to main content
Glama

BRAINIAC Insurance Underwriting & Policy Intelligence

Extract deductible structures

insurance-intelligence_deductible-structure-extract

Extract deductible/SIR amounts and apply-per structure from caller-supplied rows or local PDF text. Price $0.03 USDC. POST /api/v1/insurance-intelligence/deductible-structure-extract. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "insurance-intelligence_deductible-structure-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
filesNo
limitsNo
lossRunsNo
policiesNo
premiumsNo
exclusionsNo
deductiblesNo
requirementsNo
evidenceItemsNo
requiredEvidenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does add genuinely useful operational facts — pricing at $0.03 USDC, the POST path, and that unpaid calls return 402 and do not execute. It omits permissions, error behavior beyond 402, limits on input size, and anything about what the response contains, which matters for a 15-parameter no-annotation tool.

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?

Four short sentences, front-loaded with the action and input source, with no filler. It is efficiently written, though the brevity is achieved partly by omitting information a complex tool needs.

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?

For a tool with 15 parameters, deeply nested object arrays, no annotations and no output schema, the definition leaves the majority of the contract undocumented. An agent can tell what the tool does broadly but not how to populate most of the input or what constraints govern the extract.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 15 parameters, so the description must compensate and largely does not. It explains the csv/json/text/file(s) row-or-PDF input paths in general terms but says nothing about asOf, limits, lossRuns, policies, premiums, exclusions, deductibles, requirements, evidenceItems, or requiredEvidence, nor how those nested arrays relate to the extraction.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Extract deductible/SIR amounts and apply-per structure', plus the accepted input sources (caller rows or local PDF text). It is clear what the tool produces, though it never differentiates itself from siblings such as policy-limit-compare or coverage-gap-detect that also touch limit/deductible data.

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?

Implies usage by naming the accepted input types, which tells an agent when the tool applies, but gives no explicit when-to-use/when-not guidance and no comparison to the other insurance-intelligence tools. Choosing between this and policy-limit-compare is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources