Skip to main content
Glama

StatuteWire

get_coverage

Read-only

Lists every exclusion source and every state license source with its status today: live, not live, or information only. No key needed, free, returns no provider data. Use it before screening to know what a result can and cannot cover. A source that is not listed as live is not checked.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/closed-world annotations, the description discloses access requirements (no key needed, free), output substance (returns no provider data), the status vocabulary, and the critical caveat that an unlisted-as-live source is not checked. That last point is essential behavioral context an agent could not infer from annotations alone.

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?

Four short sentences, front-loaded with what is returned, followed by cost/access, workflow placement, and the key caveat. Every sentence carries distinct information and none repeat structured fields.

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

Completeness5/5

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

For a parameterless, non-destructive read tool with no output schema, the definition covers what is returned, how statuses should be interpreted, and the limitation that non-live sources are not checked. Nothing an agent needs in order to call and interpret it correctly is missing.

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?

The tool takes zero parameters, so there is nothing for the description to add at the parameter level, and the baseline for a parameterless tool applies. The schema coverage is complete and no compensating explanation is needed.

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?

The description uses a specific verb and resource: it lists exclusion sources and state license sources with a per-source status of live, not live, or information only. It also disambiguates scope by stating it returns no provider data, which clearly separates it from the screening tools in the sibling set.

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?

"Use it before screening to know what a result can and cannot cover" gives explicit sequencing guidance and a clear purpose in the workflow. It does not name a specific sibling alternative or state when not to use it, so it stops short of full routing guidance.

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