Skip to main content
Glama
nyc-council-mcp

nyc-council-mcp

Where this server's data comes from

about_data
Read-only

Explains where NYC Council data comes from, how current and accurate it is, and how to check or cite it by data topic or tool.

Instructions

Where this server's data comes from and how far to trust it. For each kind of data: who publishes it and a link, whether it is an official record or BetaNYC's curation, how it was gathered, what BetaNYC changed (for example cleaned, address-matched, merged or counted), how current it is on this server, what it covers and what is missing, the terms of use and the credit line to print, where to check a figure at the official source, where to report an error (to the publisher, or in this server), which tools use it, and corrections that touched it. Call it whenever someone asks where an answer comes from, how current or accurate it is, or how to check or cite it. topic narrows it to one kind of data, or to the data behind one tool (give the tool's name). For who built this server, use about_betanyc. Topics on this server: live, bills, votes, events, committees, districts, party, wikidata, social.

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

Input Schema

NameRequiredDescriptionDefault
topicNoOne kind of data (a source id), or a tool name for the data behind that tool. Any case. Default: all.

Output Schema

NameRequiredDescriptionDefault
noteYes
topicYes
serverYes
topicsYes
catalogYes
sourcesYes
left_outYesSources in the file that this server cannot show, and why
source_fileYesDATA-SOURCES.json on GitHub
contact_emailYesBetaNYC's monitored address for questions and error reports about this data, from DATA-SOURCES.json. Null when the file names none yet
who_built_thisYesCall about_betanyc for who built this server

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.9.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is already covered; the description adds what the content actually contains (publisher and link, official record vs BetaNYC curation, transformations like address-matching or counting, gaps, terms of use, credit line, error-reporting route, corrections history). It falls short of disclosing response shape or size, but with read-only annotations and an output schema that burden is lighter.

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-loads the purpose, then usage trigger, then alternative, then valid values — a sensible order with no filler sentences. The middle inventory of returned fields is long and parenthetical asides ('cleaned, address-matched, merged or counted') push it toward denseness, though each item is substantive rather than decorative.

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?

For a one-parameter read-only metadata tool with a full schema and an output schema, the definition covers purpose, triggers, sibling routing, and valid parameter values. The inclusion of return-value detail is redundant with the output schema but does not leave any calling decision unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only says the single topic parameter takes 'a source id, or a tool name ... Default: all'; the description adds what it means to pass a tool name and, critically, enumerates the valid topics (live, bills, votes, events, committees, districts, party, wikidata, social), which are otherwise absent since no enum is defined. That is meaningful value beyond the schema.

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 resource and scope: provenance, currency, coverage, terms of use and credit for each kind of data on the server. It also distinguishes itself from the nearest sibling by name: 'For who built this server, use about_betanyc.' An agent can tell it apart from about_betanyc and from the data tools without opening a 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 trigger set ('whenever someone asks where an answer comes from, how current or accurate it is, or how to check or cite it') and an explicit exclusion routing to about_betanyc for server authorship. That is the when-to-use, the when-not-to-use, and the alternative in one place.

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