Skip to main content
Glama

Don of Debt Portfolio Tools

State judgment facts

judgment_state_facts
Read-onlyIdempotent

[agencies] For one state (or DC): judgment life and renewal, post-judgment interest rule, assignment-of-judgment filing, and licensing notes — each with a verified/unverified flag, source URL, and check date. Unverified items are leads for counsel, not conclusions.

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": "judgment_state_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter state code (DC included)

Output Schema

NameRequiredDescriptionDefault
nameYes
roleYes
toolYes
as_ofYes
stateYes
noticeYes
datasetYes
sourcesYes
audienceYes
next_stepYes
disclaimerYes
educationalYes
counsel_noteYes
licensing_notesYes
assignment_filingYes
unverified_topicsYes
input_aliases_appliedYes
post_judgment_interestYes
judgment_life_and_renewalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the description only needs to add context. It does: it discloses the per-item verification flag, source URL, and check date, and warns that unverified entries are leads rather than conclusions — meaningful caveats beyond the structured metadata. It stops short of noting coverage gaps or missing-state behavior.

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?

One dense sentence plus a short caveat, front-loaded with the audience tag and scope. Every clause names a distinct returned fact, though the em-dash list is heavy enough that a reader must parse carefully.

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?

An output schema exists, so return-value documentation is not required, and the description still previews the payload shape and its trust caveat. For a single-parameter read tool this is essentially complete; only the absence of guidance on states with thin or missing data is a residual gap.

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?

With a single required parameter at 100% schema description coverage and a full enum, the schema carries the semantics. The description adds only the '(or DC)' clarification, which the enum already encodes, so this is the baseline case.

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 scope (one state or DC) and enumerates exactly what is returned: judgment life and renewal, post-judgment interest rule, assignment-of-judgment filing, and licensing notes. This content profile is clearly distinct from siblings like judgment_interest_estimate (a calculator) or state_regulator_sources, so an agent can route without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The '[agencies]' tag and the closing 'Unverified items are leads for counsel, not conclusions' give real interpretive guidance on how to treat output. However, there is no explicit when-to-use versus when-not, and no named alternative for related questions (e.g., computing an interest amount), leaving selection partly inferred.

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