Skip to main content
Glama

Read an insurance guide

read_insurance_guide
Read-onlyIdempotent

Read one guide in full as Markdown, by the slug that search_insurance_guides returns. Quote its answer and cite its url; say which policy may respond, subject to policy terms, never that a loss is covered.

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": {
      "slug": "<slug>"
    },
    "name": "read_insurance_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe guide's slug, e.g. cg-40-47-generative-ai-exclusion-robots.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real context beyond that: the payload is the full guide rendered as Markdown, and there are compliance-style constraints on how the content must be presented ('say which policy may respond, subject to policy terms, never that a loss is covered'). It does not describe behavior on a missing or malformed slug.

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 sentences, front-loaded with the operation and its output format before the usage constraints. Every clause carries information, though the second sentence packs several semicolon-separated rules together and reads more like a policy checklist than a definition.

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 one fully documented parameter, no output schema, and annotations covering the safety profile, the description supplies what is needed: what it returns (full Markdown), where the input comes from, and how to present the result. Only error behavior for an unknown slug is left unaddressed.

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% and the single parameter already carries an example, so the baseline is 3. The description earns an extra point by documenting provenance — the slug is the identifier returned by search_insurance_guides — which tells the agent how to obtain a valid value rather than invent one.

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 ('Read one guide in full as Markdown') plus scope ('one', 'in full', 'as Markdown'), and explicitly ties itself to the sibling that produces the input ('by the slug that search_insurance_guides returns'). An agent can distinguish it from search_insurance_guides 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 Guidelines4/5

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

Makes the entry condition clear: this is the follow-up call once search_insurance_guides has yielded a slug, and it prescribes how to use the result (quote the answer, cite the url, hedge on coverage). It stops short of stating when not to use it or what to do if the slug is invalid, so it falls short of a 5.

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