Skip to main content
Glama

CE / CME requirements by state

get_ce_requirements

Look up state CE renewal requirements for a profession, including hours per cycle, mandatory topics, reporting rules, and the state board legal source.

Instructions

License renewal requirements for a profession in a US state: hours per cycle, mandatory topics, reporting, state board and legal source, as published by the state board.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "profession": "<profession>",
      "state": "<state>"
    },
    "name": "get_ce_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter US state code, e.g. TX
professionYesProfession id, e.g. physicians, nurses, nurse-practitioners, pharmacists

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does useful work by naming the return payload fields and the provenance ('as published by the state board'), functioning as a stand-in for the missing output schema, but it omits coverage limits, not-found behavior, and whether data exists for every state.

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?

One sentence, front-loaded with what is being looked up, followed by the concrete output inventory. Every clause carries information and nothing is padded.

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 two-parameter read-only lookup whose parameters are fully described by the schema, the definition is nearly self-sufficient, and the field inventory substitutes for the absent output schema. A note on coverage across states or on invalid profession/state pairs would make it complete.

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% and both parameters are documented in the schema, including the two-letter state constraint and profession id examples. The description adds only the notion that state means a US state; it supplies no additional semantics such as the canonical profession id list beyond what the schema already shows.

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 resource and scope: 'License renewal requirements for a profession in a US state,' and enumerates the returned content (hours per cycle, mandatory topics, reporting, board, legal source). An agent can tell this is a domain lookup distinct from the conference-oriented siblings, though the description never names or contrasts them.

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?

Usage is implied by the phrasing — a point lookup once you know a state and profession — but there is no explicit when-to-use framing, no guidance on where valid profession ids come from (list_reference-like discovery), and no statement about unsupported profession/state combinations.

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