Skip to main content
Glama

Loa Healthcare Pricing

by io.github.aanari

Entity Prices

get_entity_prices
Read-onlyIdempotent

Return source-labeled prices for a Loa hospital or provider entity slug using the shared resolver. Use search_entities first if the slug is unknown. Results include provenance and explicit unavailable rows for requested CPT codes with no current price.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesExact Loa entity slug from search_entities or a Loa SEO page.
limitNoMaximum number of prices, default 50, max 100.
cpt_codesNoOptional CPT codes to filter. If omitted, returns current indexed prices up to the limit.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYes
entityYes
pricesYes
provenanceYes

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint and idempotentHint. Description adds that results include provenance and explicit unavailable rows for missing CPT codes, which is valuable beyond the structured annotations.

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?

Three sentences, front-loaded with the core purpose, no redundancy. Each sentence adds distinct value.

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?

Given the annotations and output schema, the description covers essential behavior (provenance, unavailable rows) and usage context. Could mention limit behavior or edge cases, but overall sufficient for effective use.

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%, so parameters are already documented. Description adds minor context for slug (where to get it) but does not significantly enhance the schema descriptions for limit or cpt_codes.

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 returns source-labeled prices for a Loa entity slug, specifying verb and resource. Distinguishes from siblings by mentioning the shared resolver and prerequisite search_entities.

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 advises to use search_entities first if the slug is unknown. While it doesn't exhaustively list when not to use, this provides clear context for a common scenario.

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