Skip to main content
Glama

MedaRep

What is loaded

coverage
Read-onlyIdempotent

States loaded, procedure family keys by market segment, DME and prescribing categories, data years, and the caller's plan limits.

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

Input 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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new context about payload content — data years, market segments, DME/prescribing categories, and the caller's plan limits — which tells the agent what it will learn and that results are per-caller scoped.

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?

A single front-loaded sentence with no filler, but the lead-in "States loaded," reads as an editing error and forces a second pass to parse; restructuring as "Reports what data is loaded: ..." would cost nothing and read cleanly.

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 and no parameters, the description's job is largely to enumerate what comes back, and it does that across five distinct content categories including plan limits. It falls short only on how to act on the result and how it relates to family_coverage.

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 the baseline is 4; there is nothing for the description to disambiguate beyond confirming the call is argument-free.

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 loaded ... data years, and the caller's plan limits" tells an agent this is a metadata/introspection tool that reports what datasets, categories and entitlements are available. The opening clause ("States loaded, procedure family keys...") is grammatically garbled, and it never distinguishes itself from the sibling family_coverage, whose name suggests overlapping scope.

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 usage is only implied: an agent can infer it is a discovery/status call to make before querying data, but there is no explicit "call this first when..." or "do not use for X, use family_coverage instead" guidance. Given the confusingly similar sibling name, an explicit boundary would have been valuable.

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