Skip to main content
Glama

New York medical board disciplinary actions: search

health_state_medical_board_ny
Read-only

New York medical board disciplinary actions (NYS DOH Board for Professional Medical Conduct open data since 1990): search physicians and physician or specialist assistants by license number or name for every public action: date, license type, action (revocation, suspension, probation...) and case summary. An empty result means no public action; it is not a licence-status check. Related tools on this server, for a different need: health_state_medical_board_tx when you need Texas Medical Board license verification and disciplinary; health_state_medical_board_fl when you need Florida health-care license verification: search by name. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "health_state_medical_board_ny"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoActions, 1 to 100 (default 20), newest first
sinceNoOnly actions on/after this date, YYYY-MM-DD
offsetNoSkip this many (paging)
lastNameNoLast name (exact, case-insensitive)
firstNameNoFirst name starts with
licenseNumberNoNY license number, e.g. 191312

Output Schema

NameRequiredDescriptionDefault
countNo
offsetNo
sourceNo
actionsNo
checkedAtNo
noActionOnRecordNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond by disclosing the data source and its 1990 start, the empty-result semantics, the cost ($0.002 per successful call), the payment mechanism (x402 USDC on Base/Solana plus 10 networks) and that failed calls are free. Those billing and result-interpretation details are exactly what annotations cannot convey.

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?

The core capability and its caveat are front-loaded, and the sibling routing and pricing follow in an orderly way. The single long opening sentence packing source, coverage, matching mode and return fields is dense, but no sentence is 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?

With an output schema present, return-value explanation is not required, and the description still supplies source provenance, empty-result meaning, pricing and sibling routing. Only pagination interplay (limit/offset ordering) is left entirely to the schema, which is a minor gap.

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 description coverage is 100%, so every parameter (limit, since, offset, lastName, firstName, licenseNumber) is already documented with format and matching semantics. The description adds only the searchable dimensions at a high level ('by license number or name') and no syntax beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource: search physicians and physician/specialist assistants in NY Board for Professional Medical Conduct open data by license number or name, returning date, license type, action and case summary. It explicitly distinguishes the scope from the Texas and Florida siblings, so an agent can choose between them without opening a schema.

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

Usage Guidelines5/5

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

Gives both when-to-use and when-not-to-use: names the tx and fl siblings with the condition that selects each, and warns that an empty result means no public action rather than a licence-status check. That negative guidance prevents a realistic misuse.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources