Skip to main content
Glama

Clinicaltables

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Npi Organization

npi_organization
Read-onlyIdempotent

"Find a hospital / clinic by name" / "look up NPI for [organization]" / "what's [Mayo Clinic]'s NPI" / "verify a healthcare facility" — search the NPPES NPI registry for organizational providers (~1.8M entries) — hospitals, clinics, group practices. Same shape as npi_individual. terms can be org name, NPI, or city.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dfNoComma-separated display fields to use in the `displays` array. Default varies per table; usually the canonical name.
efNoComma-separated extra fields to include per match. Known fields: name.full,addr_practice.full,licenses.taxonomy.classification.
countNoMaximum matches to return. Default 7, max 500. Use 1–3 for typeahead UX, 20–50 for browsing.
termsYesSearch query — prefix/contains match against canonical names. Whitespace-split into AND tokens. Example: "mayo clinic".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "count": 3,
+    "terms": "mayo clinic"
+  }
+]
  2. Changed7 schema fields changed
    • addedInput schema / properties / count / default
      Added value: +7
    • addedInput schema / properties / count / description
      Added value: +"Maximum matches to return. Default 7, max 500. Use 1–3 for typeahead UX, 20–50 for browsing."
    • addedInput schema / properties / count / maximum
      Added value: +500
    • addedInput schema / properties / count / minimum
      Added value: +1
    • addedInput schema / properties / df / description
      Added value: +"Comma-separated display fields to use in the `displays` array. Default varies per table; usually the canonical name."
    • addedInput schema / properties / ef / description
      Added value: +"Comma-separated extra fields to include per match. Known fields: name.full,addr_practice.full,licenses.taxonomy.classification."
    • addedInput schema / properties / terms / description
      Added value: +"Search query — prefix/contains match against canonical names. Whitespace-split into AND tokens. Example: \"mayo clinic\"."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: the NPPES registry source, the ~1.8M entry scale, the same-shape relationship to npi_individual, and that terms can be an org name, NPI, or city.

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?

The description is compact and front-loaded with example user intents, then gives the registry scope, sibling relationship, and valid term types. Every sentence contributes useful information without 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?

For a read-only search tool with four parameters fully described in the schema, the description covers the main invocation context: registry source, entity type, query term varieties, and relationship to npi_individual. It does not describe the return shape in detail, but 'same shape as npi_individual' partially addresses that, and no output schema exists to require more.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful parameter semantics by stating terms can be an organization name, NPI, or city, which goes beyond the schema's 'prefix/contains match against canonical names' and helps an agent form valid queries.

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?

The description clearly states the tool searches the NPPES NPI registry for organizational providers, with concrete user-intent examples like 'Find a hospital / clinic by name' and 'look up NPI for [organization]'. It also distinguishes the scope from the sibling npi_individual by specifying hospitals, clinics, and group practices.

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?

The quoted example queries provide clear context for when to use this tool, and 'Same shape as npi_individual' points to a related sibling tool. It does not explicitly state 'use this for organizations and npi_individual for individuals', but the organizational-provider scope makes the intended use clear.

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

All Clinicaltables toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources