Skip to main content
Glama

Ny Authority Debt Search

ny_authority_debt_search
Read-onlyIdempotent

Search New York municipal bond and debt issues sold by public authorities, state authorities, local authorities, Industrial Development Agencies and Local Development Corporations. Returns the issuing authority, the project financed, bond closing date, par amount split into new money and refunding, true interest cost, term, tax-exempt or taxable status, competitive or negotiated sale, and a link to the authority's own official statement. Answers "what bonds did the Dormitory Authority issue", "New York tax-exempt issues over $100 million", "who financed this project". This is primary-market issuance as reported to the Authorities Budget Office; reported secondary-market trade prices are not included, and most municipal bonds trade too infrequently to have a current price at all.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 3,
      "authority": "Dormitory",
      "min_amount": 100000000
    },
    "name": "ny_authority_debt_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax issues to return (default 50, max 500).
sinceNoEarliest bond closing date, YYYY-MM-DD.
untilNoLatest bond closing date, YYYY-MM-DD.
projectNoFree-text match on the financed project name.
authorityNoIssuing authority name, matched loosely, "Dormitory" finds "Dormitory Authority of the State of New York".
min_amountNoMinimum total par amount in dollars.
type_of_debtNoFree-text match on the debt type, e.g. "General Obligation", "Revenue".
taxable_statusNoe.g. "Tax Exempt" or "Taxable".
authority_classNoRestrict to one class: state | local | ida | ldc. Omit to search all four.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / authority / description
      Previous value: -"Issuing authority name, matched loosely — \"Dormitory\" finds \"Dormitory Authority of the State of New York\"."New value: +"Issuing authority name, matched loosely, \"Dormitory\" finds \"Dormitory Authority of the State of New York\"."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-redundant behavior: the data source (primary-market issuance as reported to the Authorities Budget Office) and the explicit limitation that secondary-market trade prices are absent, which prevents an agent from promising current pricing.

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 what is searched and then what is returned, ending with the important scope caveat. The middle sentence is a long, comma-chained field list that could be tightened, but no sentence is filler and the ordering is logical.

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?

For a nine-parameter search tool with no output schema, the description covers the data source, the returned attributes, the covered issuer universe, and the coverage limitation. The only real gap is the absence of guidance on when to prefer the totals, profile, or coverage siblings, which is a routing rather than a completeness issue.

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% with per-field descriptions for all nine parameters, including the loose-match behavior of 'authority' and the enum values for 'authority_class', so the schema carries the load. The description restates return fields rather than clarifying filter semantics, adding little beyond the schema; baseline 3 applies.

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 (Search) and a precisely scoped resource (New York municipal bond and debt issues sold by public authorities, state/local authorities, IDAs and LDCs). The enumerated issuer classes make it unmistakable what universe is searched, and the example questions ('what bonds did the Dormitory Authority issue') pin the intent further.

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?

Example questions plus the explicit scope exclusion ('reported secondary-market trade prices are not included, and most municipal bonds trade too infrequently to have a current price') tell an agent when this tool applies and when it does not. It does not name the sibling totals/profile/coverage tools as alternatives for aggregate or single-issuer questions, so routing between the four ny_authority_debt_* tools is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.