Skip to main content
Glama

Upcoming meetings and agendas

upcoming_meetings
Read-onlyIdempotent

What a city has scheduled next — council, planning commission and board meetings in the coming days, with start time, location, how to comment, and the agenda where one is posted (headline and items when summarized).

WHEN: 'What's on the agenda next week?', 'When does the planning commission meet?', 'Is the council voting on X soon?'. WHEN NOT: For what already happened, use whats_changed or search_meetings. For the full text of a posted agenda, use search_documents or open agenda_url.

Most meetings are posted before their agenda: agenda_status: 'not_posted' means the city has not published it yet, not that the meeting has no business. A cancelled meeting is listed so you can say so.

EXAMPLES: { "city": "lehi-ut" } { "city": "lehi-ut", "days": 30, "meeting_types": ["planning"] }

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity slug (e.g. 'lehi-ut'). Omit to cover every city this account can query.
daysNoHow many days ahead, from today. Default 14, max 60.
limitNoMax meetings returned, soonest first. Default 50.
meeting_typesNoOnly these meeting types, matched case-insensitively as a substring (e.g. ['council'] keeps 'City Council' and 'Council Work Session').

Output Schema

NameRequiredDescriptionDefault
periodYes
meetingsYes
truncatedYesTrue when more meetings matched than `limit`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavioral nuances: agenda_status 'not_posted' means the city has not published the agenda yet, not that the meeting has no business, and cancelled meetings are listed intentionally. It also states what fields are included, such as start time, location, comment instructions, and agenda headline/items when summarized.

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?

The description is front-loaded with the core purpose, followed by WHEN/WHEN NOT sections, important caveats, and compact examples. Every section earns its place and the structure makes routing decisions fast.

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?

Given an output schema, annotations covering safety, and full parameter schema coverage, the description supplies the remaining context an agent needs: scope, alternatives, agenda_status semantics, cancelled-meeting behavior, and examples. Nothing critical is missing.

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 the schema already fully documents city, days, limit, and meeting_types. The description's examples show typical usage but do not add meaningful semantics beyond what the schema provides.

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?

The description opens with a specific verb-and-resource statement: what a city has scheduled next, covering council, planning commission and board meetings. It clearly distinguishes the tool from siblings by naming search_meetings and whats_changed for past events and search_documents for full agenda text.

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?

It provides explicit WHEN examples ('What's on the agenda next week?', 'When does the planning commission meet?') and WHEN NOT guidance routing the agent to whats_changed, search_meetings, search_documents, or agenda_url. The alternatives and conditions are named directly.

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