Skip to main content
Glama

Search insurance guides

search_insurance_guides
Read-onlyIdempotent

Search Rayon's library of plain-English insurance guides: robot deployments, RaaS agreements, additional insured status, ISO generative AI exclusions (CG 40 47, CG 40 48, CG 35 08), marketplace seller requirements and certificates. Returns titles, one-line answers and links. An empty query lists every guide. General information, not advice on a specific policy.

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": {
      "query": "<query>"
    },
    "name": "search_insurance_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost guides to return.
queryYesWords that must all appear, e.g. 'additional insured' or 'CG 40 47'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: the shape of results (titles, one-line answers, links), the empty-query listing mode, and a scope disclaimer. It omits ranking/relevance behavior but that is minor for a search tool.

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?

Three tight sentences, front-loaded with the resource and scope, then return shape, then the edge case, then the disclaimer. Every clause carries information an agent can act on; nothing is repeated from the schema or annotations.

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 no output schema, the description responsibly summarizes what comes back, and it covers the required query parameter's edge case. Minor gaps remain around result ranking and whether the one-line answers are excerpts of the linked guides, but nothing blocks correct invocation.

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 both parameters are already documented, including the 'words that must all appear' semantics and an example. The description still adds meaning beyond the schema by explaining the empty-query case and by giving topical example queries ('additional insured', 'CG 40 47') that match real usage.

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 ('Search Rayon's library of plain-English insurance guides') and enumerates the topical coverage, from robot deployments to ISO generative AI exclusions. It also discloses the return shape ('titles, one-line answers and links'), which implicitly distinguishes it from the sibling read_insurance_guide that fetches a single full guide.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage context: an empty query lists every guide, and the closing line scopes it to general information rather than advice on a specific policy. It stops short of explicitly naming read_insurance_guide as the follow-up for full text, so the search-then-read workflow must be inferred.

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