Skip to main content
Glama

Ca Debt Issuer Profile

ca_debt_issuer_profile
Read-onlyIdempotent

Borrowing history for one California municipal bond issuer, a city, county, school district, water agency, joint powers authority or state agency. Returns total principal issued, number of issues, date range, a breakdown by debt type and by purpose, and the largest and most recent issues. Answers "how much has this California school district borrowed", "what has this city financed with bonds", "when did this agency last come to market".

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": {
      "issuer": "Los Angeles Unified School District"
    },
    "name": "ca_debt_issuer_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
issuerYesIssuer name, e.g. "Los Angeles Unified School District". Loose names are resolved.
sold_statusNo"Sold" or "Proposed". Default: both.
sale_date_toNoRestrict to issues sold on or before this date/year.
sale_date_fromNoRestrict to issues sold on or after this date/year.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description contributes beyond that by specifying the shape of the response (totals, counts, date range, debt-type and purpose breakdowns, largest and most recent issues), which matters because no output schema exists. It is silent on what happens when a loose issuer name is ambiguous or matches nothing, and on result limits, which keeps it off a 5.

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?

The definition is front-loaded with the resource and scope before moving to return contents and then example questions, with no wasted prose. The three quoted questions are mildly redundant with the return-fields sentence, but they double as intent-matching cues that plausibly aid retrieval. Sizing is appropriate for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, single-entity retrieval tool with no output schema, the description covers the input scope (who counts as an issuer), the output contents (totals, counts, ranges, breakdowns, notable issues), and the questions it answers. Nothing an agent needs in order to decide to call it and form a valid request is missing, and the sibling ca_debt_resolve_issuer handles name disambiguation.

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 all four parameters including sold_status and the sale_date bounds are already documented in the schema; the description adds nothing about their syntax or defaults. The one genuine contribution is clarifying what qualifies as an 'issuer' by listing the entity types, which helps the agent form valid names. That is marginal added meaning over a fully documented schema, so the 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?

The description names a specific resource and scope: borrowing history for exactly one California municipal bond issuer, and enumerates the covered entity types (city, county, school district, water agency, JPA, state agency). The return contents (principal issued, issue counts, date range, breakdowns, largest/most recent issues) make the tool's identity unambiguous. It stops short of naming any sibling (e.g., ca_debt_statewide_totals or ca_debt_issue) to sharpen the boundary, so it lands at 4 rather than 5.

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?

Usage context is well established through three concrete example questions ('how much has this school district borrowed', 'what has this city financed with bonds', 'when did this agency last come to market') that map directly to caller intents. There are no explicit exclusions or pointers to alternatives for adjacent tasks such as pulling a single issue or statewide aggregates, so it is clear-context-but-no-routing rather than full guidance.

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.