Skip to main content
Glama

MedaRep

What a figure means

glossary
Read-onlyIdempotent

Definitions of the published metrics: unit, source, reported or estimated, caveat, backtested accuracy, and the current data year. Cite these when explaining a number.

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

Input Schema

NameRequiredDescriptionDefault
metricsNoMetric keys (e.g. medicare_cases, forecast_cases); omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description does add value by enumerating which attributes come back for each metric, which matters since there is no output schema, but it does not describe the response shape (e.g., a list of per-metric objects) or behavior when an unknown metric key is supplied.

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. The content is front-loaded (what the tool is) followed by the action guidance (when to cite it), which is the right order for an agent scanning definitions.

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-optional-parameter read-only tool, the description is nearly sufficient: it explains what a definition contains and when to use it, compensating for the absent output schema. The only gap is not indicating how the definitions are returned or what happens on an unrecognized metric key.

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%: the metrics array is already documented as metric keys with the example values and the 'omit for all' default. The description names some of the covered concepts (unit, source, etc.) but adds no new meaning about the parameter itself, so the baseline of 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?

The description states a specific resource (definitions of the published metrics) and enumerates the fields each definition carries: unit, source, reported vs estimated, caveat, backtested accuracy, data year. An agent immediately knows this is a metric glossary rather than a data-query tool. It does not explicitly contrast itself with siblings such as coverage or company_profile, which keeps it at a 4.

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?

"Cite these when explaining a number" gives a concrete trigger condition for invocation, which is more than most definitions offer. It stops short of stating when not to call it or naming an alternative, so it does not reach 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