AI Agent Liability Insurance

AI agent liability insurance — what's covered

get_ai_liability_coverage_info

Read-only

Describes the AI agent liability insurance Johal Insurance Brokers (licensed US broker) can quote: Technology E&O with affirmative AI coverage for companies that build or deploy AI agents. Returns coverages, limits, eligible states, required quote fields and how binding works. 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_ai_liability_coverage_info"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedOct 31, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so 'Free, no side effects' largely restates structured data. The description does add real behavioral context beyond annotations: the licensing scope (US broker), the eligible-states constraint, and the fact that the response covers binding mechanics rather than just marketing copy.

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?

Two tight sentences with the product identity front-loaded and the return contents enumerated compactly. The trailing 'Free, no side effects' is somewhat redundant with the annotations and is the one phrase that does not fully earn its place.

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

Completeness5/5

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

With an output schema present and zero parameters, the description needs only to establish scope and safety, which it does. It also pre-announces the substantive sections of the response (coverages, limits, eligible states, quote fields, binding) so an agent knows what it will get.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is near 4. It spends no words on parameter meaning, which is appropriate here but adds no extra semantic value either.

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?

States a specific verb and resource ('Describes the AI agent liability insurance ... can quote') and scopes the product precisely: Technology E&O with affirmative AI coverage for companies that build or deploy AI agents. An agent can distinguish this informational tool from the quote-request sibling without opening either schema.

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: the mention of 'required quote fields' and 'how binding works' suggests reading this before requesting a quote, and 'Free, no side effects' signals it is a safe first step. However, no sibling is named and there is no explicit when-to-use versus request_ai_liability_quote or get_commercial_insurance_guide.

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

All AI Agent Liability Insurance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?