Skip to main content
Glama

Ca Debt Search Issues

ca_debt_search_issues
Read-onlyIdempotent

Search California municipal bond issuance, every state and local government bond, note, certificate of participation and Mello-Roos special-tax deal reported to CDIAC since 1984 (76,000+ issues). Filter by issuer, county, debt type, purpose, tax status, sale date and principal amount. Returns per-issue CDIAC number, issuer, issue name, sold status, principal amount, sale date, debt type, purpose, ratings, true interest cost and the underwriter, municipal advisor and bond counsel on the deal. Answers "how much debt did this California school district issue", "which California cities sold bonds this year", "what did the largest California muni deals of 2026 finance". California issuers 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": {
      "limit": 5,
      "issuer": "Los Angeles Unified School District"
    },
    "name": "ca_debt_search_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-based. Default 1.
limitNoRows to return, 1-100. Default 25.
queryNoFree-text search across issuer and issue names, e.g. "Los Angeles Unified" or "water treatment".
countyNoIssuer county, e.g. "Fresno", "Los Angeles", "San Diego".
issuerNoIssuer name; matched against CDIAC's own spelling, so "los angeles unified" resolves. Ambiguous names return candidates rather than zero rows.
sort_byNoColumn to sort on: SaleDate (default), PrincipalAmount, CDIACNumber, FinalMaturityDate, Issuer.
ascendingNoSort ascending. Default false (newest/largest first).
debt_typeNoe.g. "General Obligation Bond", "Public Enterprise Revenue Bond", "Certificate of Participation/Leases". Call ca_debt_filter_options for all 31.
tax_statusNo"Tax-Exempt", "Federally Taxable", "Alternative Minimum Tax" or "Both".
sold_statusNo"Sold" for completed sales, "Proposed" for announced but not yet sold.
issuer_groupNoe.g. "K-12 School Districts", "City Governments", "County Governments".
sale_date_toNoLatest sale date, YYYY-MM-DD or YYYY.
max_principalNoMaximum principal amount in dollars.
min_principalNoMinimum principal amount in dollars.
sale_date_fromNoEarliest sale date, YYYY-MM-DD or YYYY.
primary_purposeNoWhat the money funds, e.g. "K-12 School Facility", "Water Supply, Storage, Distribution", "Airport". 48 values.
labeled_debt_typeNoESG label: "Green", "Social Impact" or "Sustainability".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / sale_date_from / description
      Previous value: -"Earliest sale date — YYYY-MM-DD or YYYY."New value: +"Earliest sale date, YYYY-MM-DD or YYYY."
    • changedInput schema / properties / sale_date_to / description
      Previous value: -"Latest sale date — YYYY-MM-DD or YYYY."New value: +"Latest sale date, YYYY-MM-DD or YYYY."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real value beyond them: the historical coverage boundary (since 1984), the corpus size (76,000+ issues), the California-only restriction, and an explicit enumeration of returned fields including ratings, true interest cost, underwriter, municipal advisor and bond counsel. It does not mention rate limits or result-size ceilings.

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

Conciseness5/5

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

Front-loads the verb and scope, then filters, then returns, then intent examples — a logical ordering with no filler. The long enumeration of return fields earns its place because there is no output schema to carry that information.

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 17 optional parameters, no output schema and open-world annotations, the description does the necessary work: it delimits the corpus geographically and temporally and lists the return payload. The remaining gap is behavioral edge cases — what happens with ambiguous issuer names, how paging interacts with large result sets, and when a sibling tool is the better call.

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 description coverage is 100%, so every one of the 17 parameters is already documented with examples and value hints in the schema, including the forward reference to ca_debt_filter_options for the 31 debt types. The description only restates the filter dimensions generically ('issuer, county, debt type, purpose, tax status, sale date and principal amount') without adding format, matching behavior, or interaction semantics. 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 and resource ('Search California municipal bond issuance') and pins the scope precisely: every state/local government bond, note, COP and Mello-Roos deal reported to CDIAC since 1984, 76,000+ issues. It also names the boundary ('California issuers only'), which separates it from generic company or nationwide search tools. An agent knows exactly what corpus this queries without opening the 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 three quoted questions ('how much debt did this California school district issue', 'which California cities sold bonds this year', 'what did the largest California muni deals of 2026 finance') give concrete usage contexts that map to filter combinations. What's missing is routing guidance against siblings — nothing says to use ca_debt_resolve_issuer for ambiguous names or ca_debt_issuer_profile for a single-issuer rollup, both of which overlap with named intents here.

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.