Skip to main content
Glama

SolvingHealth federal health data

list_endpoints

List every API endpoint, whether it is live, and which government dataset it reads. Call this first if unsure what data is available — it also names what is deliberately NOT implemented and why, and lists open endpoints that run elsewhere, such as the family caregiver navigator.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does real work: it discloses that the result includes liveness, dataset provenance, deliberately unimplemented endpoints with reasons, and externally hosted endpoints like the family caregiver navigator. It leaves out pagination or response shape, but for a zero-parameter read-only catalog that is a minor gap.

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?

Two sentences, zero filler, and the core purpose is front-loaded before the 'call this first' directive. The second sentence is dense but every clause (not-implemented items, external endpoints) adds selection-relevant information.

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?

With no output schema, the description must convey what comes back, and it does so substantively — status, dataset mapping, gaps with rationale, and off-site endpoints. Only the output's organization or size is left unstated, which is acceptable for a zero-param listing tool.

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; the baseline applies. The description correctly implies no filtering arguments are 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?

States a specific verb and resource ('List every API endpoint') and immediately scopes the return payload: liveness status and the government dataset each endpoint reads. That distinguishes it clearly from the sibling search_* tools, which query datasets rather than enumerate the API surface.

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?

Gives an explicit trigger — 'Call this first if unsure what data is available' — which also implies the inverse case (go straight to a search tool when you already know what you want). It does not name a specific sibling as the alternative, 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.