Skip to main content
Glama

Don of Debt Portfolio Tools

State regulator and licensing sources

state_regulator_sources
Read-onlyIdempotent

[agencies] Links to the regulator, NMLS, and federal sources to check before collecting or buying debt in a state, plus the state's research note with its verified flag. Gives links only and never concludes whether a license is required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>"
    },
    "name": "state_regulator_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter state code (DC included)

Output Schema

NameRequiredDescriptionDefault
nameYes
roleYes
toolYes
as_ofYes
stateYes
noticeYes
sourcesYes
audienceYes
next_stepYes
conclusionYes
disclaimerYes
site_guideYes
educationalYes
state_linksYes
counsel_noteYes
national_linksYes
state_research_noteYes
input_aliases_appliedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's incremental value here is the explicit disclaimer that it returns links only and makes no licensing conclusion — a genuinely useful behavioral limit. Beyond that it adds no operational detail such as freshness of links or behavior when a state has no note.

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?

Two tight sentences, front-loaded with what the tool returns and followed by the limitation. The '[agencies]' tag and dense phrasing are slightly compressed but no sentence is wasted.

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 an output schema present, return values need no elaboration, and the description still flags the notable return element (the research note's verified flag). Read-only annotations cover safety; only freshness and empty-state behavior are left unaddressed for a low-complexity single-parameter tool.

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 coverage is 100% with a full state enum, so the single parameter is already fully documented by the schema. The description adds no interpretive meaning about the state code or its effect on the result, which is the expected baseline when the schema does the work.

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 (regulator, NMLS, federal source links plus the state research note and its verified flag) and scopes it per state, so an agent knows exactly what comes back. It stops short of naming a contrasting sibling (e.g. judgment_state_facts) to sharpen the boundary, leaving that to inference.

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?

It supplies a clear trigger — 'check before collecting or buying debt in a state' — which is a concrete usage context rather than a vague one. It also draws a negative boundary ('never concludes whether a license is required'), implying an agent must go elsewhere for determinations, but no alternative tool is named.

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.

Resources