Skip to main content
Glama

List valid ids

list_reference

Returns valid filter IDs for professions, specialties, states, topics, credit types, or requirements so you can build accurate CME/CE conference and renewal searches.

Instructions

Valid ids for filters: professions, specialties, states, topics, credit types, or which requirement records exist.

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": {
      "kind": "<kind>"
    },
    "name": "list_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: it does not state that this is a read-only reference lookup, whether the data is static or live, or how the result is shaped. The only behavioral hint is the phrase "which requirement records exist," implying the requirements branch reports existence rather than a plain id list.

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?

A single short sentence with no filler, and the categories are listed up front. It is slightly undermined by the awkward "or which requirement records exist" tail, which breaks parallel structure and reads as a clause grafted onto an id list.

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 one-parameter reference lookup with no output schema, the definition is close to the minimum viable: the agent knows it gets "valid ids" per category but not the concrete return shape (bare strings versus objects with id and label) or whether results are stable. Without annotations, that missing return-shape detail matters more than it would otherwise.

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 0%, so the single 'kind' parameter relies entirely on its six enum values, which the description restates (professions, specialties, states, topics, credit types, requirements). The restatement adds little beyond the enum itself, and the wording shifts confusingly to "which requirement records exist" for the last value without clarifying output format for any branch.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment "Valid ids for filters" plus an enumeration of the six reference categories conveys what the tool returns, but there is no verb and no sentence structure, so the purpose must be inferred from the tool name. It does not distinguish itself from the siblings (get_ce_requirements, get_conference, search_conferences) in any way.

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

Usage Guidelines2/5

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

"for filters" hints that this is called to populate filter values, which is an implied use case, but there is no explicit when-to-use statement, no prerequisites, and no mention of when a sibling such as search_conferences should be used instead.

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