Skip to main content
Glama

AI Agent Liability Insurance

Every question needed to quote commercial property / GL

get_submission_requirements
Read-only

Returns the full question list a carrier needs, grouped by form: ACORD 125 (applicant), ACORD 140 (property, per building), statement of values columns (3+ buildings), ACORD 126 (general liability), the class-specific supplemental for the property type, and the document list (5-year loss runs, dec page, rent roll, SOV, photos). Free, no side effects.

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": "get_submission_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNoLines wanted (default both).
property_classNoNarrow the supplemental to one class.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / property_class / enum
      Previous value: -[
      -  "apartments",
      -  "rental-homes",
      -  "hotel",
      -  "strip-center",
      -  "warehouse",
      -  "commercial-building",
      -  "gas-station",
      -  "self-storage",
      -  "condo",
      -  "lessors-risk",
      -  "other"
      -]New value: +[
      +  "apartments",
      +  "rental-homes",
      +  "small-rental",
      +  "short-term-rental",
      +  "hotel",
      +  "strip-center",
      +  "warehouse",
      +  "commercial-building",
      +  "gas-station",
      +  "self-storage",
      +  "condo",
      +  "lessors-risk",
      +  "other"
      +]
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly/destructive/openWorld, so "Free, no side effects" is a mild restatement. The real added value is behavioral detail: how results are grouped, that ACORD 140 is per building, and that a full statement of values kicks in at 3+ buildings – conditional logic the agent couldn't infer from annotations.

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

Conciseness5/5

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

A single front-loaded sentence that names the resource first, then enumerates forms with parenthetical context for each. No filler; every listed item is a genuine deliverable of the tool.

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

Completeness4/5

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

With an output schema documenting return structure and annotations covering safety, the description only needs to frame the content – which it does thoroughly via the form enumeration. Minor gap: it doesn't clarify ordering or how the class-specific supplemental is chosen when property_class is omitted.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning: it explains that a class-specific supplemental depends on property type, which connects the property_class parameter to a concrete output segment, and the line-based grouping ties to the lines parameter.

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?

Specific verb ("Returns") plus a precisely scoped resource ("the full question list a carrier needs") and it enumerates the exact forms returned: ACORD 125, 140, 126, SOV, supplemental, document list. An agent can immediately tell this is a requirements/discovery tool, distinct from sibling submission and quote tools.

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?

Usage is only implied – it reads as a pre-submission checklist lookup, but the description never says when to call it versus get_commercial_insurance_guide or the submit tools, and names no exclusions. Adequate but leaves routing 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