Skip to main content
Glama

AI Agent Liability Insurance

Send documents for a submission (loss runs, dec page, SOV…)

send_submission_documents
Destructive

Delivers base64 documents (loss runs, declarations page, SOV spreadsheet, rent roll, photos, leases) to the broker working a submission, by its CQ- reference. Up to 4 MB per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "reference": "<reference>",
      "contact_email": "<contact_email>",
      "attachments": "<attachments>"
    },
    "name": "send_submission_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoWhat these documents are.
referenceYesSubmission reference from submit_commercial_insurance_submission (CQ-…).
attachmentsYesOptional documents (≤4 MB total base64): loss runs, dec page, SOV, rent roll, photos.
contact_emailYesSame contact email used on the submission.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the grading bar is lower. The description usefully adds the 4 MB per-call ceiling and confirms delivery to an external party (the broker), which explains the open-world trait, but it never addresses the non-idempotent behavior (repeat calls re-send the same files) or what the 'destructive' flag means in this context.

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?

Two sentences, front-loaded with the action and payload, and the 4 MB constraint trailing as the key operational limit. Nothing is redundant or padded.

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 present, return values need not be described, and annotations carry the safety profile; the description covers what is sent, to whom, keyed by what. Minor residual gaps are whether the submission must pre-exist and what happens on duplicate sends, but nothing required for a correct call is missing.

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?

Schema description coverage is 100%, so every parameter (notes, reference, attachments, contact_email) is already documented with examples and the document_type enum. The description only restates the document categories and adds the 'up to 4 MB per call' total-size constraint, which the schema states per-attachment as '≤4 MB total base64'; baseline 3 applies when the schema does the heavy lifting.

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+resource: delivers base64 documents (loss runs, dec page, SOV, rent roll, photos, leases) to the broker on a submission identified by a CQ- reference. The 'by its CQ- reference' phrasing implies it operates on an existing submission, which quietly separates it from submit_commercial_insurance_submission, but no sibling is named explicitly.

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 implied rather than stated: you send documents against a submission that already exists, presumably created by submit_commercial_insurance_submission. There is no explicit when-to-use/when-not guidance, no mention that the submission must exist first, and no direction on alternatives such as attaching documents at submission time.

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