Skip to main content
Glama

Ca Debt Issue

ca_debt_issue
Read-onlyIdempotent

Full detail for one California municipal bond issuance by its CDIAC number (the YYYY-NNNN identifier CDIAC assigns each issue), including everything the search tool summarises plus issuance costs broken out by participant, underwriter takedown and expenses, municipal advisor fee, bond counsel and disclosure counsel fees, trustee fee, rating agency fee, plus call dates, final maturity, credit enhancement, statutory authority, and any Annual Debt Transparency Report rows filed against the issue in later years. Answers "what did this California bond deal cost to issue and who was paid".

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": {
      "cdiac_number": "2026-0936"
    },
    "name": "ca_debt_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
cdiac_numberYesCDIAC number, e.g. "2026-0936". Digits-only and spaced forms also work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real value by enumerating what the response contains beyond the search summary — cost breakouts by participant, fees, call dates, credit enhancement, statutory authority, and later-year ADTR rows — which matters because there is no output schema.

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?

Purpose and key are front-loaded, and the closing question gives a crisp retrieval trigger. The middle clause is a long comma-chained inventory of fields, which is dense but each item is substantive rather than filler.

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 correctly takes on the burden of describing return contents and does so thoroughly. What is missing is minor: no note on what happens when a CDIAC number is unknown or malformed, despite the schema noting that digits-only and spaced forms are accepted.

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 there is only one parameter, so the baseline is already high. The description still adds meaning by spelling out that the identifier is CDIAC-assigned and uses the YYYY-NNNN form, reinforcing the schema's example rather than merely repeating it.

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 verb-and-resource statement: full detail for one California municipal bond issuance, keyed by CDIAC number. It explicitly positions itself against the sibling search tool ('everything the search tool summarises plus...'), so an agent can distinguish detail-fetch from search without opening either schema.

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 contrast with the search tool and the closing use-case question ('what did this California bond deal cost to issue and who was paid') give clear context for when to reach for this tool. It stops short of an explicit rule such as 'use ca_debt_search_issues first to find the CDIAC number, then call this', and names no exclusions.

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.