Skip to main content
Glama

Don of Debt Portfolio Tools

Forward flow vs one-time (spot) sale explainer

forward_flow_vs_spot
Read-onlyIdempotent

[lenders] Explains the two common sale structures for charged-off portfolios: a one-time (spot) sale and a forward-flow agreement, with seller and buyer considerations and the OCC Bulletin 2014-37 context. Educational only.

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

Input Schema

NameRequiredDescriptionDefault
perspectiveNo

Output Schema

NameRequiredDescriptionDefault
roleYes
toolYes
as_ofYes
noticeYes
sourcesYes
summaryYes
audienceYes
boundaryYes
next_stepYes
disclaimerYes
educationalYes
perspectiveYes
forward_flowYes
one_time_saleYes
input_aliases_appliedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safe-read profile is fully covered structurally. The description adds the useful behavioral boundary 'Educational only' (not advice, not a valuation) plus the topical scope of what it will discuss. With annotations carrying the safety burden, this is adequate but not rich — it does not say how the explanation is structured or how perspective affects output.

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 front-loaded sentence opens with the audience tag, then the resource, then the two structural options being contrasted. Every clause carries information with no filler; it is appropriately short for an educational explainer.

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-value shape need not be described, and the tool is a single-optional-parameter explainer with no side effects. The description covers subject matter, authority (OCC Bulletin 2014-37), and the educational-only limit, which is close to sufficient; the only real gap is the unmentioned perspective parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single optional 'perspective' parameter (enum seller/buyer/both) is never mentioned in the description. The enum values are largely self-explanatory, but the description does not say what changes when a perspective is chosen or what the default behavior is. With low coverage the description was expected to compensate and does not.

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 concrete subject (two sale structures for charged-off portfolios: one-time/spot sale vs. forward-flow agreement) with the specific subject matter it covers (seller and buyer considerations, OCC Bulletin 2014-37 context). An agent can distinguish it from transactional siblings like sale_readiness_check or buy_box_builder because of the explicit 'educational only' framing, though no sibling is named directly.

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 bracketed '[lenders]' audience tag and 'Educational only' do convey context and the absence of transactional intent, which helps an agent route conceptual 'what is the difference' questions here rather than to a readiness or pricing tool. However, there is no explicit when-to-use vs. alternative guidance (e.g., versus asset_class_guide or faq_search), so the routing signal is implied rather than stated.

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