Skip to main content
Glama

get_meeting_calendar

Read-only

Retrieves upcoming Utah State Legislature meetings, filterable by date range and committee name, so agents can identify scheduled hearings and plan accordingly. Times are returned in UTC.

Instructions

Upcoming legislative meetings (times in UTC; Utah is UTC-7/-6).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax items to return (1-50).
offsetNoStart position for paging; use next_offset from a prior call.
end_dateNoYYYY-MM-DD; meetings on/before this date.
committeeNoOnly meetings whose committee name contains this.
max_charsNoCharacter budget for this response (500-20000). Defaults to the server setting.
start_dateNoYYYY-MM-DD; meetings on/after this date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context that returned times are in UTC and that Utah local time is UTC-7/-6, which prevents misreading of results. It does not mention paging, default limits, or what a meeting record contains, so it goes beyond but not far beyond the annotations.

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 parenthetical sentence with essentially no wasted words, and the timezone caveat is front-loaded. The tradeoff is that it reads as a fragment rather than a structured statement of what the tool returns.

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 read-only list tool with six fully documented parameters and no output schema, the schema carries most of the burden, and the description covers the timezone interpretation risk. Still, it says nothing about paging behavior beyond the schema hint or about what fields a meeting entry exposes, leaving the agent to discover result shape empirically.

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 all six parameters (limit, offset, start_date, end_date, committee, max_chars) are already documented in structured form, and the baseline is 3. The UTC note indirectly clarifies how date-filter boundaries and returned meeting times should be interpreted, but adds no per-parameter detail.

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 phrase 'Upcoming legislative meetings' identifies the resource and implies a list/get operation, but no explicit verb is given and the word 'upcoming' is slightly misleading because the schema exposes start_date/end_date filters that can retrieve past meetings. An agent can guess the intent, but it isn't stated precisely.

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?

No guidance on when to call this versus alternatives, and no prerequisites or exclusions are mentioned. The only sibling that isn't a direct match is get_committee, and nothing here helps an agent decide between listing meetings and fetching committee details.

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