Skip to main content
Glama

BRAINIAC Certificate of Insurance

Grade certificate coverage gaps

coi_coverage-grade

Compare a caller-supplied certificate of insurance, as text or JSON, with the minimum limits, endorsements, and expiry date in the request. The grade is the share of each minimum that is missing. The text is not a PDF and the result is not a coverage opinion. Price $0.04 USDC. POST /api/v1/coi/coverage-grade. 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": {
      "certificate": "<certificate>",
      "requirements": "<requirements>"
    },
    "name": "coi_coverage-grade"
  }
}

Input Schema

NameRequiredDescriptionDefault
certificateYes
requirementsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/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 add real behavior: a $0.04 USDC price, the 402 failure mode where the call does not execute, and a scope disclaimer that the result is not a coverage opinion. It does not disclose auth mechanics, idempotency, retry semantics, or what the graded response actually contains, which matters for a paid endpoint.

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 core comparison and grade definition, followed by disclaimers, price, and the failure mode. The endpoint path line is marginally redundant but nothing is padded or buried.

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

Completeness3/5

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

There is no output schema and no annotations, so the description must cover both meaning and behavior; it does explain what the grade means but not the response shape, per-line-item breakdown, or error codes other than 402. For a nested two-object paid tool with zero field documentation, this is adequate but leaves real gaps.

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 0% and both top-level parameters are nested objects with roughly a dozen undocumented fields. The description partially compensates by explaining that 'certificate' accepts free text or JSON and that 'requirements' holds minimum limits, endorsements, and an expiry date, which maps onto fields like additional_insured, waiver_of_subrogation, and expires_after — but it never explains individual fields such as umbrella, workers_compensation, or the date format.

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 gives a concrete verb and resource: compare a caller-supplied certificate of insurance against minimum limits, endorsements, and expiry, and it defines the output ('the grade is the share of each minimum that is missing'). The only gap is that it never positions itself against the sibling coi_analyze, so an agent must infer which of the two to pick.

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?

It conveys input-mode conditions (text or JSON), an exclusion ('the text is not a PDF'), and a payment precondition (unpaid calls return 402 and do not run). However, there is no explicit when-to-use guidance or named alternative, leaving the choice between grading and analysis 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