Skip to main content
Glama

Don of Debt Portfolio Tools

Chain-of-title checklist

chain_of_title_checklist
Read-onlyIdempotent

[lenders] Checklist for tracing charged-off accounts from the originator through each transfer to the current seller. Answer yes/no/unknown per item and give the number of known transfers; returns status, open questions, and the Don of Debt chain-of-title guide. A document-consistency review, not a legal conclusion.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chain_of_title_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
gaps_explainedNoAny apparent gaps explained in writing for counsel review
known_transfersNoNumber of known transfers after origination
schedule_or_exhibitNoSchedule, exhibit, or account-level extract tied to each transfer document
originator_identifiedNoOriginator (original creditor) identified for the pool
assignment_each_transferNoAssignment documents for each known transfer
entity_changes_documentedNoName changes, mergers, or successor entities documented
transfer_dates_consistentNoTransfer and effective dates consistent across documents
bill_of_sale_each_transferNoBill of sale for each known transfer
account_references_reconcileNoAccount references reconcile across schedules and the current tape

Output Schema

NameRequiredDescriptionDefault
roleYes
toolYes
as_ofYes
noticeYes
sourcesYes
audienceYes
boundaryYes
checklistYes
next_stepYes
disclaimerYes
educationalYes
open_questionsYes
known_transfersYes
documents_expectedYes
input_aliases_appliedYes
useful_reconciliation_fieldsYes

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 readOnly, idempotent, closed-world, non-destructive behavior. The description adds that the tool returns status, open questions, and a guide, and clarifies it is a document-consistency review rather than a legal conclusion—useful context beyond annotations.

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 well-structured sentences front-load the purpose and follow with output summary and a caveat. No unnecessary words, though the first sentence is somewhat dense.

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?

Given nine parameters with full schema descriptions, an output schema, and rich annotations, the description provides adequate context: what the tool does, what it returns, and a key limitation. It does not need to enumerate parameters or return fields.

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% and all nine parameters have descriptive schema text. The description only briefly restates the answering format ('yes/no/unknown per item') and the transfer count, adding little beyond what the schema already provides.

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?

The description states a specific verb and resource: 'Checklist for tracing charged-off accounts from the originator through each transfer to the current seller.' It clearly scopes the tool to chain-of-title document review, distinguishing it from broader diligence or document-gap tools.

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 description implies usage for lenders conducting chain-of-title reviews and notes it is 'not a legal conclusion,' but it does not explicitly state when to use this tool versus siblings like diligence_checklist or document_gap_check. Usage context is present but alternatives are not addressed.

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