Skip to main content
Glama
Sign In
nyc-council-mcp

nyc-council-mcp

by BetaNYC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_upcoming_hearings

List upcoming NYC Council committee hearings and Stated meetings in real time for scheduling, with an option to include agenda items per event.

Instructions

List upcoming NYC Council committee hearings and Stated meetings. Real-time data — use this for scheduling, not the local index. Each event's EventItems array is populated with its agenda items (the bills/matters on the agenda) via a follow-up call per event; pass include_agenda=false to skip that and return events faster with EventItems empty.

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_upcoming_hearings"
  }
}

Input Schema

NameRequiredDescriptionDefault
days_aheadNoHow many days ahead to look (default 14, max 90)
include_agendaNoWhether to populate each event's EventItems (agenda items) via a per-event follow-up call (default true). Set false for a faster response when you only need the hearing schedule, not what's on each agenda.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.7.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of disclosure, and it does this well: it reveals that EventItems are populated by a separate follow-up call per event, along with the resulting cost to deal with latency, and how to avoid that cost. It says nothing about pagination, rate limits, or the fields on each event, so it falls short of full behavioral coverage.

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 front-loaded sentences: purpose first, data freshness second, and the expensive-option caveat last. The final sentence largely duplicates the include_agenda schema text, which is mild redundancy, but everything else earns its place.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple 2-parameter read tool with no output schema and no annotations, and the description covers what is returned at a high level (events plus their agenda items) and the cost tradeoff of the main flag. What is absent is the shape of an event object and any ordering or pagination detail, which is a minor gap for a list tool.

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 coverage is 100%, so the schema already documents both parameters, including the default 14 / max 90 day range. The description restates the include_agenda tradeoff rather than adding format or edge-case meaning beyond the schema, so it fits the baseline of 3.

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 uses a specific verb plus resource: 'List upcoming NYC Council committee hearings and Stated meetings.' It scopes the result set (upcoming, NYC Council, hearings and Stated meetings), which is distinct from the other get_*/search_* legislative lookup tools the agent can see.

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?

It gives explicit when-to-use guidance ('use this for scheduling, not the local index') and a conditional ('pass include_agenda=false ... when you only need the hearing schedule'). It doesn't say when another visible sibling such as get_committee or get_bill would be the better choice, so routing guidance is not complete.

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

Deploy Server

Other Tools