Skip to main content
Glama

List procedures

list_procedures
Read-onlyIdempotent

Lists the procedures covered by OpenHealth, such as knee replacement, hip replacement, heart bypass and cataract surgery, with each procedure's id and OpenHealth page. Shows which procedures have doctor ratings and which do not. Use it to find the procedure id for a doctor search. This tool takes no input.

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

Output Schema

NameRequiredDescriptionDefault
dataNo
notesNo
statusYes
sourcesNo
page_urlNo
release_idNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered structurally. The description adds genuine context beyond that: it takes no input, it reports which procedures have doctor ratings and which do not, and each entry includes a page link. It does not discuss result size or ordering, but an output schema exists to carry return shape.

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?

Three tight sentences, front-loaded with the resource and its contents, then the usage trigger, then the no-input confirmation. The four example procedures are slightly more than strictly necessary but aid recognition of the domain vocabulary.

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 tool with rich annotations and an existing output schema, the description covers everything an agent needs: what is listed, what fields come back, the ratings distinction, and how to use the result. Nothing material 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?

There are zero parameters, so the baseline is 4, and the closing sentence "This tool takes no input" explicitly confirms the empty schema rather than leaving the agent to infer it. No further parameter meaning is possible here.

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 ("Lists the procedures covered by OpenHealth") and enumerates concrete examples plus what each entry carries (id and OpenHealth page). It also implicitly separates itself from find_doctors_for_procedure by framing itself as the id-lookup step for a doctor search.

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 to find the procedure id for a doctor search" gives a clear positive trigger and signals the prerequisite relationship to the doctor-search flow. It stops short of naming an explicit alternative or when-not-to-use condition, which keeps it from 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