Skip to main content
Glama

get_coverage_guide

Fetches a plain-English car insurance coverage guide by slug, or lists all six guides when no slug is given. Use it to explain limits, state minimums, and shopping options.

Instructions

Retrieve one of Insurance Panda's six plain-English car insurance guides (or list all guides if no slug is provided).

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_coverage_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoOptional guide slug. Omit to list all six guides.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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. "Retrieve" implies a safe read and "plain-English" hints at prose content, but it says nothing about what actually comes back (guide body text versus metadata), how large it is, or whether content is static. It is adequate but thin for a zero-annotation tool with no output schema.

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?

A single sentence with the primary mode front-loaded and the fallback mode in a parenthetical. Every clause earns its place and nothing is redundant.

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 one-optional-parameter, non-destructive retrieval tool, the definition covers both modes and the resource scope. The only real gap is the absence of any indication of the returned content, which matters slightly more because there is no output schema.

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 coverage is 100% and the enum already enumerates all six valid slugs, while the schema's own field description already says to omit it for a full listing. The description adds essentially nothing beyond that, so the baseline 3 applies.

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 pairs a specific verb ("Retrieve") with a specific resource ("one of Insurance Panda's six plain-English car insurance guides") and covers both invocation modes. It does not name or distinguish itself from siblings such as get_state_minimums, so it stops short of a 5.

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?

The parenthetical states the alternate branch clearly: omit the slug to list all guides. However, it gives no guidance on when an agent should reach for this guide tool versus the sibling tools that serve state-minimum data, leaving the main routing decision implicit.

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