Claim Back

List the appeal guides

list_guides

Read-onlyIdempotent

Lists Claim Back’s guides (US), each with its slug, title, one-line summary and link. Medicare Advantage: how to appeal and who can ask, the appeal deadline, a prior authorization denial, the fast appeal when care is ending, care ended or denied because the patient stopped improving (the maintenance standard), and the independent review. Long-term care insurance: what to do after a denial, and the independent review of benefit-trigger denials state by state. Use it to find the guide that answers the user’s question, then read_guide.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context: the four fields returned per item (slug, title, summary, link), which tells the agent exactly what it can use to pick a guide. Missing only list size or whether the set is static, a minor gap for a fixed catalogue.

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?

Front-loaded with purpose and return shape, ending with the call-to-action toward read_guide. The middle topical enumeration (Medicare Advantage, maintenance standard, state-by-state review) runs long and partly duplicates what the per-item summaries will show, but it does earn its place by letting the agent match a user question to a guide without a second call.

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 zero-parameter read-only listing with no output schema, the description supplies the scope (US), the per-item fields, and the next step. Nothing needed to invoke 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 and schema coverage is 100%, so the baseline is 4. There is no parameter meaning to add, and the description correctly does not invent any filtering options that do not exist.

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?

Opens with a specific verb and resource ("Lists Claim Back's guides (US)") and immediately enumerates what each entry contains: slug, title, one-line summary and link. This makes it unmistakably the discovery/listing tool, distinct from read_guide and appeal_deadline.

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

Usage Guidelines5/5

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

The closing sentence gives an explicit workflow: "Use it to find the guide that answers the user's question, then read_guide." That names the alternative and the condition that selects it, so the agent knows this is the entry point before fetching a specific guide.

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

All Claim Back tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?