Skip to main content
Glama

Don of Debt Portfolio Tools

Charged-off asset class guide

asset_class_guide
Read-onlyIdempotent

[buyers] For one charged-off asset class (same asset enum as every other tool): the record story, the documentation focus, typical documents, and the Don of Debt guide link (the asset-class hub where no dedicated guide exists).

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_class": "<asset_class>"
    },
    "name": "asset_class_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_classYesAsset 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

Output Schema

NameRequiredDescriptionDefault
roleYes
toolYes
as_ofYes
guideYes
labelYes
noticeYes
sourcesYes
audienceYes
next_stepYes
disclaimerYes
asset_classYes
educationalYes
record_storyYes
routing_noteYes
typical_documentsYes
documentation_focusYes
input_aliases_appliedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds that the response is narrative reference content plus an external guide link, which is useful framing. It does not mention anything about the fallback behavior when no dedicated guide exists beyond the link, nor about size or caching.

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?

A single sentence, front-loaded with the audience tag and the unit of work, with no filler. It is dense with internal jargon ('record story', 'Don of Debt guide') that costs a little comprehension, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one fully described enum parameter and an output schema present, the description needn't explain return values, and it is adequate on that bar. However, terms like 'record story' and 'Don of Debt guide link' are unexplained, and for a reference-lookup tool the agent gets no sense of what the guide actually contains beyond a topic list.

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% with the full enum and legacy aliases documented, so the schema carries the parameter burden and baseline is 3. The description adds one useful semantic: exactly one class per call, and it reinforces that the enum is shared across all tools, which tells the agent the value is portable between calls.

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 the resource (a guide for one charged-off asset class) and enumerates the payload: record story, documentation focus, typical documents, and the guide link. The parenthetical 'asset-class hub where no dedicated guide exists' distinguishes it from a fuller per-class guide, so an agent can tell what it gets. It never states the verb plainly ('returns'), leaving the action implied rather than explicit.

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 '[buyers]' audience tag and 'for one charged-off asset class' imply the lookup context, and the hub parenthetical hints at when this is the fallback resource. There is no explicit when-to-use/when-not language and no named alternative among siblings (e.g. document_gap_check or diligence_checklist) for an agent to route to instead.

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