Skip to main content
Glama

verify_nurse_license

Verify nurse license status, expiration dates, qualifications, and enforcement actions across US states (FL, NY) using official state nursing board data.

Instructions

Verify a nurse's license across US states (FL, NY). Search by license number or name. Returns license status, expiration, qualifications, and enforcement actions from official state nursing boards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYesUS state code: FL (Florida DOH MQA), NY (New York NYSED)
licenseNumberNoLicense number to look up (e.g. "RN9414870" for FL, "825282" for NY)
lastNameNoLast name for person name search
firstNameNoFirst name for person name search (optional)
licenseTypeNoLicense type filter: RN, LPN, NP, APRN, CNA
limitNoNumber of results to return (max 25)

Implementation Reference

  • Handler function for verify_nurse_license tool.
      async ({ state, licenseNumber, lastName, firstName, licenseType, limit }) => {
        const params = new URLSearchParams();
        params.set("state", state);
        params.set("limit", String(limit));
        if (licenseNumber) params.set("licenseNumber", licenseNumber);
        if (lastName) params.set("lastName", lastName);
        if (firstName) params.set("firstName", firstName);
        if (licenseType) params.set("licenseType", licenseType);
    
        const url = `${BACKEND_URL}/nurse-license/verify?${params.toString()}`;
        const res = await fetch(url);
        const data = await res.json();
    
        if (!data.success) {
          return {
            isError: true,
            content: [{ type: "text", text: `Error: ${data.error}` }],
          };
        }
    
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      }
    );
  • Schema definition for verify_nurse_license tool.
    {
      state: z
        .enum(["FL", "NY"])
        .describe("US state code: FL (Florida DOH MQA), NY (New York NYSED)"),
      licenseNumber: z
        .string()
        .optional()
        .describe('License number to look up (e.g. "RN9414870" for FL, "825282" for NY)'),
      lastName: z
        .string()
        .optional()
        .describe("Last name for person name search"),
      firstName: z
        .string()
        .optional()
        .describe("First name for person name search (optional)"),
      licenseType: z
        .string()
        .optional()
        .describe("License type filter: RN, LPN, NP, APRN, CNA"),
      limit: z
        .number()
        .int()
        .min(1)
        .max(25)
        .default(10)
        .describe("Number of results to return (max 25)"),
    },
  • src/index.ts:227-282 (registration)
    Tool registration for verify_nurse_license.
    server.tool(
      "verify_nurse_license",
      "Verify a nurse's license across US states (FL, NY). Search by license number or name. Returns license status, expiration, qualifications, and enforcement actions from official state nursing boards.",
      {
        state: z
          .enum(["FL", "NY"])
          .describe("US state code: FL (Florida DOH MQA), NY (New York NYSED)"),
        licenseNumber: z
          .string()
          .optional()
          .describe('License number to look up (e.g. "RN9414870" for FL, "825282" for NY)'),
        lastName: z
          .string()
          .optional()
          .describe("Last name for person name search"),
        firstName: z
          .string()
          .optional()
          .describe("First name for person name search (optional)"),
        licenseType: z
          .string()
          .optional()
          .describe("License type filter: RN, LPN, NP, APRN, CNA"),
        limit: z
          .number()
          .int()
          .min(1)
          .max(25)
          .default(10)
          .describe("Number of results to return (max 25)"),
      },
      async ({ state, licenseNumber, lastName, firstName, licenseType, limit }) => {
        const params = new URLSearchParams();
        params.set("state", state);
        params.set("limit", String(limit));
        if (licenseNumber) params.set("licenseNumber", licenseNumber);
        if (lastName) params.set("lastName", lastName);
        if (firstName) params.set("firstName", firstName);
        if (licenseType) params.set("licenseType", licenseType);
    
        const url = `${BACKEND_URL}/nurse-license/verify?${params.toString()}`;
        const res = await fetch(url);
        const data = await res.json();
    
        if (!data.success) {
          return {
            isError: true,
            content: [{ type: "text", text: `Error: ${data.error}` }],
          };
        }
    
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      }
    );
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the data sources ('official state nursing boards') and return information types (status, expiration, qualifications, enforcement actions), but doesn't mention rate limits, authentication requirements, error conditions, or whether this is a read-only operation. It provides basic behavioral context but lacks operational details.

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 efficiently structured in two sentences: first establishes purpose and scope, second details search methods and return values. Every element serves a clear purpose with zero wasted words, making it easy to parse quickly.

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 6-parameter tool with no annotations and no output schema, the description provides good foundational context about what the tool does, supported states, search methods, and return data. However, it doesn't explain the relationship between licenseNumber and name parameters (are they alternatives? can both be used?), nor does it describe the output format beyond listing data types.

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 the schema already documents all 6 parameters thoroughly. The description mentions 'search by license number or name' which aligns with parameters but doesn't add meaningful semantic context beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 specific action ('verify'), target resource ('nurse's license'), and scope ('across US states (FL, NY)'). It distinguishes from sibling tools by focusing on nurse license verification rather than population reports, marketplace searches, or contractor licenses.

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 description provides clear context for when to use this tool (verifying nurse licenses in FL or NY states) and mentions two search methods (by license number or name). However, it doesn't explicitly state when NOT to use it or provide direct alternatives among sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lulzasaur9192/marketplace-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server