Skip to main content
Glama

Describe the Verzi Medicare coverage server

server_info
Read-onlyIdempotent

Name, canonical endpoint, and support contact for this server. Says which tools need a plan that includes receipts. No sign-in required.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

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 and closed-world, so safety needs no restating. The description adds genuinely new behavior: no sign-in is required, and the output discloses which tools need a receipt-inclusive plan, which is useful pre-flight context.

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 short sentences covering returned fields, a notable output flag, and auth requirements — front-loaded and waste-free. The middle sentence about receipt-inclusive plans is slightly oblique but earns its place as planning guidance.

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 an output schema present, the description need not enumerate return fields, and it still names the key ones plus the no-auth condition and the plan-gating hint. For a zero-argument metadata tool this is nearly everything an agent needs to call it confidently.

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, which is the baseline-4 case; the description correctly spends no space on argument explanation and instead describes the payload rather than inputs.

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?

The description enumerates the concrete fields returned (name, canonical endpoint, support contact), which tells an agent exactly what this tool yields and implicitly sets it apart from action-oriented siblings like search or check_dme_coverage. It is a noun-phrase listing rather than a verb-led statement, but the resource is unambiguous.

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?

The description implies a discovery/metadata use case but never states when to call it versus alternatives such as list_data_sources or get_documentation_requirements. No exclusions or triggering conditions are given, so the agent must infer the entry point.

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