Skip to main content
Glama

ClinX open data: 340B and health centers

About the data

about_the_data
Read-onlyIdempotent

What ClinX's open data holds (the 340B tables and the health center sets), where each part comes from, when each was last brought up to date or read, what the marks in a health center report mean, the licence, and where to download the files whole.

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

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 establish readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds real value beyond that by disclosing what the response actually contains — provenance, freshness dates, legend semantics, licence terms, and bulk-download pointers — which tells the agent this returns explanatory text rather than records. It does not describe format or structure of the reply, which keeps it below a 5.

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?

It is a single sentence with the primary scope front-loaded (what the open data holds) followed by the supporting items. The parenthetical list is dense but each element — provenance, freshness, legend, licence, download — carries distinct information. Slightly run-on, but no sentence is wasted.

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 input parameters and no output schema, the description bears the burden of explaining what comes back, and it does so by enumerating the categories of information returned. For a reference/about tool of low complexity this is close to sufficient; only the shape of the returned content and whether it covers every dataset is left unstated.

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 per the baseline this dimension starts at 4. The description correctly implies a parameterless, single-shot call and introduces no parameter concepts that would need schema backing.

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 contents of the tool: the 340B tables, health center sets, provenance, last-updated/last-read timestamps, report legend meanings, licence, and whole-file download locations. That makes it unambiguous that this is a metadata/documentation lookup rather than a data query, so an agent can distinguish it from siblings like get_health_center_report or find_health_centers. It stops short of a single crisp verb+resource statement, reading more as a content inventory.

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?

Usage is only implied: the listed contents (field meanings, freshness, licence, download) suggest consulting it to interpret or qualify results from the data tools, but the description never says when to call it or when not to. No alternative tool is named or ruled out, leaving the agent to infer that this is a preamble/reference call.

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.