Skip to main content
Glama

Search US CME conferences

search_conferences

Search upcoming US CME and CE conferences by profession, specialty, location, format, topic, and dates to identify relevant continuing education events.

Instructions

Find upcoming US CME conferences and CE meetings (physicians, NPs, PAs, nurses, pharmacists, dentists, psychologists, social workers, veterinarians). Filters combine with AND. Use list_reference for valid ids.

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

Input Schema

NameRequiredDescriptionDefault
toNoLatest start date, YYYY-MM-DD
fromNoEarliest start date, YYYY-MM-DD (default: today)
limitNoMax results, default 20
queryNoWords to match in title, series, organizer or city, e.g. 'cardiology' or 'Hawaii'
stateNoTwo-letter US state code, e.g. FL
topicNoMandatory CE topic id, e.g. opioid_prescribing, implicit_bias
cruiseNotrue = only CME cruises
formatNo
specialtyNoSpecialty id, e.g. cardiology, family-medicine, dermatology
professionNoProfession id, e.g. physicians, nurse-practitioners, physician-assistants, nurses

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. 'Filters combine with AND' is a genuinely useful behavioral disclosure the schema does not provide, and 'upcoming' implies the default from-date. However, nothing is said about result ordering, pagination beyond limit, or that this is a read-only lookup with no side effects.

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?

Three short sentences, front-loaded with purpose, then filter behavior, then the id-lookup pointer. The parenthetical profession list is long but serves disambiguation for the profession filter, so little is wasted.

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?

For a 10-parameter, annotation-free search tool with no output schema, the description covers purpose, filter combination, and id sourcing but leaves the result shape and ordering unexplained. It is adequate to invoke correctly but not fully complete.

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 90%, so the schema already documents most parameters and the baseline is 3. The description adds real value by stating that filters combine with AND and by routing id-valued filters (topic, specialty, profession) to list_reference, which the per-parameter descriptions do not say.

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 ('Find upcoming US CME conferences and CE meetings') and scopes it to the US, which distinguishes it from get_conference (single record) and list_reference (id lookup). An agent can tell what this returns without opening the schema.

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 sentence 'Use list_reference for valid ids' gives an explicit precondition for the id-based filters (topic, specialty, profession), and 'upcoming' signals the default time window. It stops short of stating when NOT to use this tool or when get_conference is preferable.

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