Skip to main content
Glama
nyc-council-mcp

nyc-council-mcp

About BetaNYC and this server

about_betanyc
Read-only

Provides BetaNYC background, contact channels, event and donation links, and GitHub issue paths for reporting bugs or requesting features, plus server version details.

Instructions

Who built this server and how to reach them: BetaNYC, a project of the Fund for the City of New York. Returns what BetaNYC is, links to its events, newsletter and donation page, where to report a bug in this server or ask for a new feature (this server's GitHub issues), and this server's name and version.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
aboutYes
linksYes
serverYes
historyYes
supportYes
built_byYes
whats_changedYes
bugs_and_requestsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.9.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description goes beyond them by disclosing the categories of content returned (identity, links, issue tracker, version), which is the main thing an agent needs to know before invoking it. It says nothing about output format or pagination, but for a static informational endpoint that gap is minor.

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?

It is a single sentence with the key idea front-loaded and no filler, but the tail becomes a dense comma-separated list of links (events, newsletter, donation, GitHub issues) that could read more crisply. Every element is relevant, so nothing is wasted, but the structure is list-like rather than sharply prioritized.

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 zero-parameter, read-only informational tool with an output schema already documenting the return shape, the description supplies everything an agent needs: what the tool is about and what categories of information come back. Nothing material is missing for correct invocation.

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?

There are zero input parameters, so parameter semantics is at the baseline of 4. The schema is fully described and there is nothing the description could add on this dimension.

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 framing ('Who built this server and how to reach them') and then enumerates exactly what the tool returns: BetaNYC's identity, events/newsletter/donation links, the GitHub issues channel for bugs and feature requests, and the server's name and version. That is concrete enough to separate it cleanly from the data-query siblings, none of which serve a metadata/contact role.

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?

The content list makes the use case clear: call this when an agent needs maintainer identity, contact/support links, or the server version. There are no explicit exclusions or pointers to alternatives (e.g., that data questions belong to about_data or the request tools), but the purpose is narrow enough that the intended trigger is unambiguous.

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