Skip to main content
Glama

Fetch one Verzi Medicare coverage page

fetch
Read-onlyIdempotent

Fetch one public Verzi page by id (code:E0601, lcd:L33718, article:A52467, or denials:E0601). Returns the page title, text, and verzi.health URL. No sign-in required. Codes only, no patient data.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPage id: code:E0601, lcd:L33718, article:A52467, or denials:E0601

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower; the description still adds real value by disclosing the auth profile ('No sign-in required'), the returned payload (title, text, URL), and the PHI exclusion ('Codes only, no patient data'). It stops short of describing behavior for a missing or invalid id.

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?

Three short sentences, front-loaded with the action and scope, then the return values, then the access/data constraints. No wasted prose.

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 single-parameter read tool with an output schema and full annotation coverage, the definition covers purpose, id format, auth, and data-sensitivity scope. Only edge-case behavior (nonexistent id, malformed prefix) is unaddressed, which is minor given the schema pattern.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the id field already documents the accepted prefixes with a regex pattern and example. The description restates the same prefix list, adding little beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource ('Fetch one public Verzi page by id') and enumerates the id prefixes, so the agent knows exactly what it returns. It does not name the sibling `search` as the way to discover ids, so the boundary with that alternative is left implicit.

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

Usage Guidelines3/5

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

'Fetch ... by id' implies the precondition of already holding an id, and 'No sign-in required. Codes only, no patient data' gives useful context. But there is no explicit when-to-use/when-not guidance or pointer to `search` for id discovery.

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