Skip to main content
Glama

Discover category and topic filters

discover_meeting_vocabulary
Read-only

Discover the valid category and topic filter values before filtering a search.

Meeting `category_tag`s are opaque UUIDs and topics have no fixed list, so you
cannot guess them. Call this first to get the real values, then pass a returned
`category_tag` (from `categories[].tags`) or `topic` string into
`search_meetings_semantic` / `list_recent_meetings`. Scope with a government
and/or date range; calls without explicit dates default to a recent window
(returned as `default_window_days`).

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

Input Schema

NameRequiredDescriptionDefault
end_dateNoOptional latest date, MM-DD-YYYY.
start_dateNoOptional earliest date, MM-DD-YYYY.
topic_limitNoMax topics to return, most common first (1-200).
government_idNoOptional account_id to scope the vocabulary to one government.
government_idsNoOptional list of account_ids to scope to several governments. Overrides government_id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive), and the description adds real behavioral context: values are opaque UUIDs, topics have no fixed list, and calls without explicit dates fall back to a recent window returned as default_window_days. This is genuinely useful beyond the annotations, though not exhaustive.

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?

Front-loaded with the action and rationale, then the downstream routing and scoping note. Every sentence carries distinct information with no padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 values need not be restated, and all five parameters are documented in the schema. The description supplies the missing 'why' and 'when', leaving nothing an agent needs to call it correctly.

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 100%, so the baseline is 3, but the description adds meaning: it explains the government/date scoping intent and the default-window behavior when start_date/end_date are omitted, which the schema alone does not convey.

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 ('Discover the valid category and topic filter values') and explains why the tool exists (values cannot be guessed). It clearly differentiates itself from the search/list siblings it feeds into.

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?

Explicitly says to 'Call this first' and names the downstream alternatives ('search_meetings_semantic' / 'list_recent_meetings') with the exact arguments to pass. When-to-use is unambiguous.

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