Skip to main content
Glama

List SaveWell procedures

list_procedures
Read-only

List the outpatient procedures SaveWell compares for people with Original Medicare, with the id to pass to find_care.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real domain scope (only Original Medicare, only outpatient procedures SaveWell compares), which prevents misuse for other insurance types. It says nothing about whether the list is paginated or how large it is, but with annotations carrying the rest, this is adequate.

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?

One sentence, front-loaded with the verb and resource, with the downstream use of the id appended rather than buried. No filler or restatement of the tool name.

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 zero-parameter, read-only list tool with no output schema and one sibling, the description covers what it returns (procedure ids) and the population constraint. The only minor gap is not indicating the size/shape of the returned list, which matters little given there is no output schema to lean on.

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 disambiguate; baseline 4 applies. The description appropriately spends its words on the result's purpose (the id) instead of inventing parameter guidance.

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?

A specific verb ('List') plus a precisely scoped resource ('outpatient procedures SaveWell compares for people with Original Medicare'). It also names the sibling find_care as the consumer of the returned id, so the agent can place it in the workflow, though it stops short of a full explicit contrast with that sibling.

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?

'...with the id to pass to find_care' makes the intended usage sequence clear: call this first to obtain a procedure id, then feed it to find_care. There is no explicit statement of when not to use it or what to do if the desired procedure is absent.

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