Skip to main content
Glama

Ny Authority Debt Totals

ny_authority_debt_totals
Read-onlyIdempotent

Aggregate New York public authority borrowing by year and by authority class, total par issued, how much was new money versus refunding, and the most active issuers. Answers "how much did New York authorities borrow in 2024", "which New York issuers borrow the most", "how much of this is refinancing". Primary-market issuance only.

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": {
      "top": 5,
      "since": "2023-01-01"
    },
    "name": "ny_authority_debt_totals"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoHow many top issuers to return (default 15).
sinceNoEarliest bond closing date, YYYY-MM-DD.
authority_classNoRestrict to one class: state | local | ida | ldc. Omit for all four.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered and the description need not repeat it. The one piece of genuine added context is the "Primary-market issuance only" data-scope constraint, which tells the agent results will exclude secondary-market activity. It does not cover freshness/lag of the underlying data, aggregation units, or auth needs, so with annotations doing most of the work a 3 is appropriate.

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 core purpose, then the returned dimensions, then the answering examples, then the scope constraint. Every sentence carries information, though the three quoted example questions are somewhat redundant with each other and with the preceding enumeration of metrics.

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 takes on the job of explaining what comes back and does so well: totals by year, by authority class, new-money vs refunding split, and a ranked issuer list. Combined with a fully documented three-parameter schema, this is enough for an agent to call the tool correctly; only data currency and the default 'since' window are left unstated.

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?

Schema coverage is 100% and each of the three parameters (top, since, authority_class) is already documented, including the enum values for authority_class in the schema. The description does add semantic framing by stating the outputs are grouped "by year and by authority class", which clarifies what since and authority_class actually control in the result. That is modest added value over a schema that already does the heavy lifting – baseline-plus rather than baseline.

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?

Names a specific verb and resource: aggregates New York public authority borrowing, and enumerates the dimensions returned (year, authority class, total par, new money vs refunding, top issuers). An agent can tell it produces summary totals rather than individual bond records, which implicitly distinguishes it from the debt_search and debt_profile siblings, though no sibling is named explicitly.

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 example questions ("how much did New York authorities borrow in 2024", "which issuers borrow the most", "how much is refinancing") map directly onto use cases, and the closing "Primary-market issuance only" line sets a clear boundary for when this tool is not appropriate. No named alternative tool is offered when the user needs secondary-market or individual-bond data, which keeps it out of 5 territory.

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.