Skip to main content
Glama
WillHsiaoNYC

NYC Open Data Capital Projects MCP Server

by WillHsiaoNYC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_agencies

Read-onlyIdempotent

List NYC capital-project agencies with a schedule-executor flag to resolve agency roles and filter results by name.

Instructions

Agency dictionary with live CPD presence + schedule-executor flag.

Interpretation rules:

  • [agency_roles] Agency attribution is role-aware: an agency's projects mean its sponsor (owner) view, except DDC/DCAS/EDC default to managing (builder). State the returned agency_scope. managing_agency is the executor on schedules and the budget-holder on budgets; a budget-only holder is not a schedule executor. list_agencies exposes is_schedule_executor. For sponsor-scoped budget totals, use a semi-join to fms_sponsor; a value-bearing join can multiply lines. Co-owner totals can overlap and must not be added together.

  • [presence] Presence in a selected reporting snapshot means reportable at that period. There is no separate active flag. Historical presence or a latest-known row does not prove presence in the current complete snapshot. A completed project can retain an open budget line for years; presence does not mean construction is in progress.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
containsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
agenciesYes
provenanceYes
interpretation_rulesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "InterpretationRule": {
+      "properties": {
+        "id": {
+          "description": "Stable identifier of the domain rule.",
+          "title": "Id",
+          "type": "string"
+        },
+        "text": {
+          "description": "Guidance for interpreting and reporting this tool's result.",
+          "title": "Text",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "text"
+      ],
+      "title": "InterpretationRule",
+      "type": "object"
+    }
+  },
+  "additionalProperties": true,
+  "properties": {
+    "agencies": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "title": "Agencies",
+      "type": "array"
+    },
+    "interpretation_rules": {
+      "items": {
+        "$ref": "#/$defs/InterpretationRule"
+      },
+      "title": "Interpretation Rules",
+      "type": "array"
+    },
+    "provenance": {
+      "additionalProperties": true,
+      "title": "Provenance",
+      "type": "object"
+    }
+  },
+  "required": [
+    "provenance",
+    "interpretation_rules",
+    "agencies"
+  ],
+  "title": "AgenciesResult",
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, closed-world tool. The description adds substantial behavioral context beyond that: how presence is determined, that there is no active flag, that historical presence is not current presence, and that role attribution and co-owner totals have non-obvious semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and labeled with bracketed rules, but it is dense and jargon-heavy for a one-parameter dictionary tool. Many sentences carry useful domain caveats, though some could likely live in output schema documentation instead of invocation guidance.

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

Completeness3/5

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

An output schema exists, so return field structure need not be described. The description supplies rich domain semantics for interpreting results, but it completely omits the 'contains' parameter and offers no guidance on when to use this tool over related tools, leaving invocation context incomplete.

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

Parameters1/5

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

The input schema has one parameter, 'contains', with 0% schema description coverage, and the description never mentions it. No meaning, expected format, or filtering behavior is provided for the only invocation parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence identifies the resource as an 'Agency dictionary' with two specific returned fields: live CPD presence and a schedule-executor flag. That is more specific than a generic list tool, though the acronym CPD is unexplained and the description does not explicitly contrast the tool with siblings beyond domain notes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives extensive interpretation rules for returned data, but it does not explicitly say when to call list_agencies versus alternatives such as run_sql, dataset_info, or list_categories. The semi-join note is about downstream SQL usage, not about when this MCP tool should be selected.

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