Skip to main content
Glama

MedaRep

Hospital or ASC profile

facility_profile
Read-onlyIdempotent

A hospital or ASC by CMS certification number: payer mix, inpatient DRG and outpatient procedure volumes, ASC case counts, negotiated commercial and Medicare Advantage prices for the families done there, and who operates there.

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": {
      "ccn": "<ccn>"
    },
    "name": "facility_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccnYesCMS certification number; from incumbents' sites of care or surgeon_profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description's contribution is a content inventory of what the profile returns, which is real added value. It stops short of disclosing data freshness, coverage gaps, or behavior for an unknown CCN, so with annotations carrying the rest a 3 is right.

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?

One front-loaded sentence that leads with the entity and then lists the returned data families; there is no filler. The long enumerated clause makes it slightly run-on, but every item listed is informative content rather than padding.

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, the description bears the burden of describing return values, and it does so with a concrete list of data families. Missing only edge-case behavior (invalid CCN, partial data, refresh cadence), which is a modest gap for a read-only lookup tool.

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?

There is a single parameter at 100% schema description coverage, so the baseline is 3. The phrase 'by CMS certification number' restates the schema field rather than adding format detail such as CCN length or validation behavior.

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 names the resource precisely (a hospital or ASC identified by CMS certification number) and enumerates the payload: payer mix, DRG/procedure volumes, ASC case counts, negotiated prices, and operators. That distinguishes it in substance from company_profile, practice_profile and surgeon_profile by entity type, even though it never names those siblings explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no prerequisite, and no alternative named. The only signal is the implicit 'look up a facility by CCN,' and the useful hint about where CCNs come from (incumbents' sites of care or surgeon_profile) lives in the schema, not the description.

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