Skip to main content
Glama

Don of Debt Portfolio Tools

Placement readiness check (agencies and creditors)

placement_readiness_check
Read-onlyIdempotent

[agencies] For collection agencies receiving placements, or creditors placing accounts with an agency. Answer yes/no/unknown per item (agreement, authority, validation-information fields, scrubs, SOL review, licensing, data security, complaints, remittance). Returns a checklist with primary-source links. Licensing items link to regulators only and never conclude 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": {
      "role": "<role>"
    },
    "name": "placement_readiness_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
scrubsNoBankruptcy, deceased, and dispute scrubs completed and documented
sol_reviewNoStatute-of-limitations review completed with counsel
data_securityNoInformation-security program and secure file transfer in place
account_supportNoAccount support available on request (statements, agreements, payment history)
itemization_dataNoValidation-information fields ready (itemization date, amounts, creditor names)
creditor_authorityNoDocumented authority from the account owner to place and collect
complaints_disputesNoComplaint and dispute handling process documented
licensing_confirmedNoState licensing and bonding confirmed with each regulator (links only; no conclusion here)
placement_agreementNoWritten placement or servicing agreement (scope, fees, remittance, recall rights)
reporting_remittanceNoReporting, remittance, and reconciliation schedule agreed

Output Schema

NameRequiredDescriptionDefault
roleYes
toolYes
as_ofYes
noticeYes
sourcesYes
summaryYes
audienceYes
boundaryYes
checklistYes
next_stepYes
disclaimerYes
open_itemsYes
educationalYes
input_aliases_appliedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare a safe, read-only, idempotent, closed-world operation, and the description adds real behavioral context beyond them: the yes/no/unknown answering convention, the checklist-plus-primary-source-links return, and a firm limitation that licensing items link to regulators only and never conclude whether a license is required. That scope limitation is exactly the kind of disclosure an agent needs to avoid over-claiming.

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 compact paragraph, front-loaded with the audience tag and role framing, followed by the item list and the return/limitation clause. Every sentence carries content; only the bracketed '[agencies]' label is slightly opaque.

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 shape needn't be spelled out, and the description still notes the checklist and primary-source links. With only 'role' required and all item params self-documented, an agent has enough to call it correctly; explicit sibling differentiation is the only notable omission.

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 91% and every optional item parameter carries its own description and enum, so the schema does the heavy lifting. The description contributes the answering convention and the item list, but adds no syntax or grouping detail beyond what the schema already states.

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?

Names the audience and the resource precisely: readiness items for placement between collection agencies and creditors, with the checked categories (agreement, authority, validation fields, scrubs, SOL, licensing, data security, complaints, remittance) enumerated. It does not explicitly distinguish itself from the sibling sale_readiness_check, so it stops short of a 5.

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 audience clause ('collection agencies receiving placements, or creditors placing accounts with an agency') implies when the tool applies, and the role enum reinforces the two scenarios. However, there is no explicit when-not guidance or routing to adjacent tools such as sale_readiness_check or document_gap_check.

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