Skip to main content
Glama

BRAINIAC Certificate of Insurance

Extract and check a certificate of insurance

coi_analyze

Extract PDF/image fields with confidence, then compare them with contract requirements. Uncertain OCR is WARN and is never treated as verified. Price $0.10 USDC. POST /api/v1/coi/analyze. Unpaid calls return 402 and do not run.

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": {
      "fileBase64": "<fileBase64>",
      "mediaType": "<mediaType>",
      "requirements": "<requirements>"
    },
    "name": "coi_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaTypeYes
fileBase64Yes
vendorNameNo
projectNameNo
requirementsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses pricing ($0.10 USDC), the endpoint, and that unpaid calls return 402 and do not execute — a critical pre-call fact. It also states the key output semantic that uncertain OCR is WARN and never treated as verified. It stops short of covering rate limits, file-size ceilings, or the shape of the returned comparison.

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?

Five short sentences, front-loaded with the core extract-then-compare purpose, followed by the OCR caveat and operational facts. Every sentence carries information and none is padded, though the endpoint string is of marginal use to an agent.

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?

For a complex tool this is mixed: the payment and 402 behavior plus the WARN/never-verified rule are exactly the operational context an agent needs and cannot get from the schema. However, with no output schema and no annotation coverage, the description leaves the return structure (confidence values, per-requirement pass/fail shape) and all five parameter meanings undocumented.

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 5 parameters, including a deeply nested 'requirements' object with generalLiability, umbrellaLiability, automobileLiability, and workersCompensation sub-fields, yet the description never mentions a single parameter. It does not explain what fileBase64/mediaType expect, what vendorName and projectName are used for, or how requirements entries are interpreted. The description must compensate here and does not.

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?

The description names two specific verbs and their objects — 'Extract PDF/image fields with confidence' and 'compare them with contract requirements' — which together pin down the resource as a certificate of insurance. It does not explicitly contrast itself with the sibling coi_coverage-grade, so an agent must infer the division of labor from the names alone.

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 by the two-stage framing: pass a document plus requirements and get a compliance comparison, which tells the agent the prerequisite inputs. However, there is no explicit when-to-use/when-not statement and no routing to the sibling tool for the adjacent capability.

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