YouTube & Shorts Transcript Scraper — SRT, VTT & Viral Hooks

npi_medical_registry

Read-only

CMS NPPES NPI Registry lookup for healthcare organizations and facilities (NPI-2 only, HIPAA safe harbor).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "npi_medical_registry"
  }
}

Input Schema

Name	Required	Description
`city`	No	City name
`limit`	No	Max organizations to return (default 10)
`state`	No	2-letter US state code (e.g. CA, NY, MN)
`number`	No	10-digit National Provider Identifier (NPI)
`postal_code`	No	Postal code
`organization_name`	No	Healthcare organization or facility name

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine value with the 'NPI-2 only' scope and the 'HIPAA safe harbor' compliance note, but says nothing about rate limits, pagination behavior past the limit param, or what an empty/unconstrained query returns.

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?

A single front-loaded sentence with a verb, resource, scope and compliance note; every clause earns its place and nothing is padded.

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

Completeness3/5

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

With six all-optional parameters and no output schema, the definition should say what an unconstrained call returns and roughly what fields come back (name, address, taxonomy, NPI). The compliance and scope notes help, but response behavior remains unexplained.

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 six self-documented parameters, so the schema carries the load. The 'NPI-2 only' constraint does add meaning to the 'number' parameter (individual NPIs will not match), but the description does not explain how the optional filters combine or what happens when none are supplied.

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?

States a specific verb+resource (NPI Registry lookup) and scopes it to healthcare organizations and facilities, which no sibling tool covers. The 'NPI-2 only' qualifier sharpens the target, though the description never names the API's operator beyond 'CMS NPPES'.

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

Usage Guidelines3/5

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

The 'NPI-2 only' clause implicitly excludes individual-provider (NPI-1) lookups, which is a useful boundary. However there is no explicit when-to-use guidance, no suggestion of which parameter combinations to prefer (number vs name+state+city), and no mention of alternatives for individual providers.

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

All YouTube & Shorts Transcript Scraper — SRT, VTT & Viral Hooks tools Inspect

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

Need Help?