Skip to main content
Glama

Ny Authority Debt Profile

ny_authority_debt_profile
Read-onlyIdempotent

Everything one New York public authority has issued: every bond and debt issue with its terms, plus totals by fiscal year and a breakdown of new money versus refunding. Answers "how much has the Dormitory Authority borrowed", "what has Battery Park City Authority issued and at what interest cost", "is this issuer mostly refinancing". Covers primary-market issuance only, no reported trade prices.

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": {
      "authority": "Battery Park City"
    },
    "name": "ny_authority_debt_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax issues to return (default 200, max 500).
authorityYesAuthority name, matched loosely, e.g. "Battery Park City".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the bar is lower. The description adds real scope context beyond them: primary-market issuance only, and no reported trade prices, which tells an agent what data will be absent from results. It does not mention the result cap that the schema carries (default 200, max 500).

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 the deliverable, followed by representative questions and a scope caveat. Three sentences, no filler. The example questions are slightly verbose but serve query-matching, which justifies their length.

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?

With no output schema, the description does the work of explaining returns: issue-level terms plus fiscal-year totals and a new-money/refunding split. Combined with a simple two-parameter schema, an agent has enough to call it correctly. Only the sibling routing and result-cap behavior are left implicit.

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 both 'authority' (loose name match, example provided) and 'limit' (default/max) documented in the schema. The description adds no parameter-level detail such as how loose matching behaves or what to do when an authority name is ambiguous, so baseline 3 applies.

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?

States a specific verb and resource: everything one New York public authority has issued, including each bond and debt issue with terms, fiscal-year totals, and a new-money vs refunding breakdown. The three sample questions make the scope concrete. It does not name sibling tools (search, totals, coverage), so differentiation comes from the content rather than explicit routing.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: use it for a per-issuer overview when the user asks 'how much has X borrowed' or 'is this issuer mostly refinancing'. There is no explicit when-not-to-use, and no pointer to ny_authority_debt_search, ny_authority_debt_totals, or ny_authority_debt_coverage for narrower or cross-issuer queries.

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.