Skip to main content
Glama

Ca Debt Resolve Issuer

ca_debt_resolve_issuer
Read-onlyIdempotent

Look up the exact issuer name CDIAC uses for a California municipal bond issuer from a partial or informal name, "san diego" returns the dozens of distinct issuers containing it, from the city itself to its school, port and transit districts. Use this when a name is ambiguous before searching issuance.

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": {
      "name": "san diego"
    },
    "name": "ca_debt_resolve_issuer"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull or partial issuer name, e.g. "san diego".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive behavior. The description adds meaningful non-annotation behavior: a partial name returns dozens of distinct matching issuers, including related districts, rather than a single exact match. It does not mention ordering, limits, or pagination.

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?

Two sentences, front-loaded with the operation and an illustrative result. The district examples earn their place by explaining why ambiguous names return many matches.

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 one-parameter resolver with full schema coverage and annotations covering safety, the description supplies purpose, expected input ambiguity, return behavior, and when to use it. Nothing essential is missing.

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%, so the parameter is already documented. The description still adds that the input may be informal and that the tool resolves to the exact CDIAC canonical issuer name, which goes beyond the schema's basic "full or partial issuer name."

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: looks up the exact issuer name CDIAC uses for a California municipal bond issuer. The partial/informal input and "san diego" example make the resolver behavior distinct from generic search tools.

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?

Gives a clear when-to-use condition: when a name is ambiguous before searching issuance. It does not explicitly name when not to use it or a specific alternative tool, but the intended moment is easy to infer.

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.