Skip to main content
Glama

Don of Debt Portfolio Tools

Document gap check

document_gap_check
Read-onlyIdempotent

[lenders] List which supporting documents you have for a charged-off pool (by category, not by account). Returns the documents buyers commonly ask for that are missing, why each matters, asset-specific extras, and links to the Don of Debt guides.

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": {
      "asset_type": "<asset_type>",
      "documents_available": "<documents_available>"
    },
    "name": "document_gap_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_typeYesAsset class. Shared enum across all tools; legacy aliases accepted: auto→auto-deficiency, installments→installment-loan, installment-loans→installment-loan, auto-loan→auto-deficiency, store-card→retail-card, credit_card→credit-card, personal_loan→personal-loan, telecom→telecom-utility, utility→telecom-utility
documents_availableYes

Output Schema

NameRequiredDescriptionDefault
roleYes
toolYes
as_ofYes
noticeYes
sourcesYes
audienceYes
boundaryYes
next_stepYes
asset_typeYes
disclaimerYes
educationalYes
document_gapsYes
asset_type_codeYes
documents_presentYes
input_aliases_appliedYes
asset_specific_questionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description's main added value is the scope caveat that results are category-level, not account-level, and that each gap comes with rationale and guide links. It adds no auth, rate-limit, or cost context, and much of the return-value description overlaps with the existing output schema.

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 sentences, front-loaded with the audience tag, the verb, and the scope qualifier before the return preview. Dense and low-waste, though the trailing list of return items is somewhat duplicative given an output schema exists.

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?

For a two-parameter read-only tool with full annotations and an output schema, the description covers what it does, its granularity, and the shape of the answer. The only real gap is guidance on choosing it over neighboring checklist tools.

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 50%: asset_type is well documented in the schema (including legacy aliases), while documents_available carries only an enum with no per-value explanation. The description implies documents_available is the list of documents you already hold, which is a modest semantic gain, but it does not explain how category-level entries map to the array values.

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?

States a specific verb and resource ('List which supporting documents you have for a charged-off pool') and adds a scoping qualifier ('by category, not by account') plus a preview of what comes back. It does not explicitly distinguish itself from adjacent checklist-style siblings like chain_of_title_checklist or diligence_checklist, 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 '[lenders]' audience tag and the phrase 'documents buyers commonly ask for' imply pre-sale prep usage, so the when-to-use context is inferable. There is no explicit statement of when not to use it or which sibling to pick instead (e.g., chain_of_title_checklist vs diligence_checklist).

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