Skip to main content
Glama

Don of Debt Portfolio Tools

Due diligence checklist (8 stages)

diligence_checklist
Read-onlyIdempotent

[buyers] The Don of Debt's eight-stage debt portfolio due diligence sequence: authority, ownership record, account support, data reconciliation, legal and operational flags, operating plan, economics, and purchase terms and closing. Pass a stage to get one, or none for all. Seller perspective adds preparation steps.

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

Input Schema

NameRequiredDescriptionDefault
sideNo
stageNo

Output Schema

NameRequiredDescriptionDefault
roleYes
sideYes
toolYes
as_ofYes
noticeYes
stagesYes
sourcesYes
audienceYes
boundaryYes
next_stepYes
disclaimerYes
educationalYes
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 establish readOnly, idempotent, closed-world, non-destructive behavior, so the description only needs to add beyond that. It does add one useful behavioral fact — that the seller side yields extra preparation steps — but says nothing about output shape or length variation beyond the stage selection. With an output schema present, a 3 is fair.

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?

The audience tag and core purpose are front-loaded, followed by the parameter behavior, so nothing important is buried. The long stage enumeration is somewhat redundant with the enum but earns its place by mapping terse enum keys to readable stage meanings.

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 two optional enum parameters, an output schema, and full annotations, the description covers purpose, both parameter effects, and the omission default. An agent can invoke it correctly without further context; only sibling-routing guidance 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 description coverage is 0%, so the description must compensate, and it largely does: it explains that omitting 'stage' returns the full sequence, and that 'side' changes the content (buyers vs. seller preparation steps). The stage enum values are clarified by their human-readable expansions (e.g., 'ownership record', 'data reconciliation').

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 — an eight-stage debt portfolio due diligence checklist — and enumerates the stages, so an agent knows exactly what it returns. The '[buyers]' prefix scopes the audience. It does not explicitly differentiate itself from near siblings like chain_of_title_checklist or document_gap_check, keeping it below 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?

'Pass a stage to get one, or none for all' and 'Seller perspective adds preparation steps' describe how to drive the parameters, which implies when each variant is appropriate. However, there is no explicit guidance on when to reach for this checklist versus the sibling checklists, and no stated prerequisites or exclusions.

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