Skip to main content
Glama
nyc-council-mcp

nyc-council-mcp

search_legislation_live

Search NYC Council legislation through the live Legistar API to confirm current bills when a local index may be stale. Sort by introduction date to reach older or newer legislation.

Instructions

Search NYC Council legislation via the live Legistar API. Slower than search_bills but always current — use when the local index may be stale. Multi-word queries match matters whose title contains ALL the words (in any order), so 'section 254 capital' works — you do NOT need a single generic token. Wrap a phrase in double quotes to require those words to be adjacent. Note: Legistar's OData API has no full-text relevance ranking, so results are ordered by introduction date, not by how well they match. To find OLDER legislation, set order='date_asc' (oldest first) rather than raising the limit.

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": {
      "query": "<query>"
    },
    "name": "search_legislation_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return (default 20, max 50)
orderNoSort by introduction date: 'date_desc' (newest first, default) or 'date_asc' (oldest first — use to reach historical legislation).
queryYesSearch terms. Multiple words are AND-ed (all must appear in the title/name); quote a "phrase" to require adjacency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.7.1

TDQS

A4.5/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 load and does well: it discloses the latency tradeoff versus the indexed search, and critically that OData has no relevance ranking so results are ordered by introduction date. It does not cover pagination beyond limit or any rate-limit/auth constraints, which keeps it short of a 5.

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?

Front-loaded with purpose, then the sibling comparison, then matching semantics, then ranking caveat, then the ordering tip — a sensible priority order. Slightly padded by the em-dash aside in the multi-word example, but nothing is irrelevant.

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?

Three simple parameters, no annotations, no output schema; the description covers speed, matching, ranking, and sort behavior, which is the substance an agent needs. Return shape is left implicit, acceptable for a straightforward list search but the only remaining gap.

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 real interpretation: a worked example ('section 254 capital') clarifying that AND-ed terms need no single generic token, plus the reasoning that makes order='date_asc' the correct lever for historical recall instead of a bigger limit.

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 (search NYC Council legislation) plus the backing system (live Legistar API). It also positions itself against an alternative ('Slower than search_bills but always current'), so an agent can distinguish the two without opening either schema.

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?

Gives an explicit selection rule ('use when the local index may be stale') and an explicit remedy for a common failure mode ('To find OLDER legislation, set order=date_asc ... rather than raising the limit'). Both when-to-use and a when-not-to-do-something are stated.

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