Skip to main content
Glama

Loa Healthcare Pricing

by io.github.aanari

Hospital Pricing

get_hospital_pricing
Read-onlyIdempotent

Hospital-specific pricing tool for source-labeled Loa runtime data. Returns source-labeled Published MRF prices and Loa Verified Provider Price overlays for CPT codes, including cash/self-pay and payer-negotiated rates when available. Use this when comparing named hospitals or checking a quoted hospital price against available source rows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cpt_codesYesCPT procedure codes to look up pricing for
hospital_idsYesHospital IDs from search_hospitals results

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYes
pricingYes
provenanceYes
services_foundYes
hospitals_foundYes

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint true and destructiveHint false, so the description adds value by specifying data sources (MRF, Loa verified) but does not provide additional behavioral insights beyond annotations.

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 sentences, front-loaded with purpose and use case. No redundant text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given output schema exists, description adequately explains return types (published MRF, verified overlays, cash/self-pay, negotiated rates) and use case. Complete for a read-only data retrieval 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?

Schema coverage is 100% with clear parameter descriptions. The description does not add new semantics beyond mentioning CPT codes and hospital-specific context already implied by parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it is a hospital-specific pricing tool returning source-labeled Published MRF prices and Loa Verified Provider Price overlays for CPT codes. Differentiates from siblings like get_market_pricing by emphasizing hospital-specific and named hospitals.

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?

Explicitly states when to use: when comparing named hospitals or checking a quoted hospital price. Does not mention when not to use or alternative tools for broader pricing queries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Loa Healthcare Pricing toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: search tools cover different entities, pricing tools cover different scenarios (hospital, market, estimate), and the explanation and update tools are unique. No two tools overlap in function.

Naming Consistency4/5

Most tools follow a verb_noun pattern (get_, search_, explain_, suggest_, submit_), which is clear and predictable. However, the verbs are not uniform across all tools (e.g., 'get' vs 'search' for lookups), introducing slight inconsistency.

Tool Count5/5

With 12 tools, the server is well-scoped for healthcare pricing. Each tool serves a necessary function—search, pricing variations, profile, explanation, and updates—without excess or deficiency.

Completeness5/5

The tool surface covers the full workflow: entity/code searching, multiple pricing queries, price source explanation, entity profiles, and update submissions. No obvious gaps for the intended domain.

Resources