Skip to main content
Glama

Loa Healthcare Pricing

by io.github.aanari

Provider Search

search_providers
Read-onlyIdempotent

Search public CMS NPI Registry data for clinicians and healthcare organizations by specialty, name, or location. Use returned provenance to understand the registry source and scope. Use this for provider lookup, not pricing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoProvider name to search for (e.g. "John Smith")
limitNoMax results (default 20)
locationNoLocation to search in
specialtyNoMedical specialty (e.g. "Cardiology", "Family Medicine")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
totalYes
providersYes
provenanceYes

TDQS

A4/5.0
Behavior3/5

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

Annotations cover safety (readOnlyHint, idempotentHint, destructiveHint). Description adds provenance note and data source, but no contradictions. With annotations present, a score of 3 is appropriate.

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: first states core function, second provides usage guidance. No redundancy or filler.

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 annotations and output schema, description adds enough context about data source and usage. Slightly more detail about return structure would push to 5.

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 descriptions for all parameters. Description merely lists criteria without adding extra meaning; baseline 3 is correct.

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?

Explicitly states verb 'Search', resource 'public CMS NPI Registry data for clinicians and healthcare organizations', and search criteria (specialty, name, or location). Distinguishes from sibling tools like search_entities, search_hospitals, and pricing tools via 'not pricing'.

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?

Provides clear context: 'Use this for provider lookup, not pricing.' Implicitly contrasts with sibling pricing tools, though alternatives are not explicitly named.

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