Skip to main content
Glama

Don of Debt Portfolio Tools

Buy box builder and matcher

buy_box_builder
Read-onlyIdempotent

[buyers] For debt buyers. Turns your stated criteria (asset types, age bands, placement levels, minimum media, size range, excluded states, structure) into a structured buy box, lists unanswered criteria and clarifying questions, and — if you also pass an aggregate portfolio profile — checks fit per criterion. Ends with an opt-in link to submit the buy box privately. No inventory is listed or implied.

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_types": "<asset_types>"
    },
    "name": "buy_box_builder"
  }
}

Input Schema

NameRequiredDescriptionDefault
age_bandsNo
min_mediaNo
portfolioNo
sale_typesNo
asset_typesYes
excluded_statesNo
placement_levelsNo
account_count_maxNo
account_count_minNo
face_value_max_usdNo
face_value_min_usdNo
require_in_statute_min_pctNo

Output Schema

NameRequiredDescriptionDefault
fitYes
roleYes
toolYes
as_ofYes
noticeYes
buy_boxYes
sourcesYes
audienceYes
next_stepYes
disclaimerYes
educationalYes
inventory_noteYes
readiness_promptsYes
opt_in_introductionYes
unanswered_criteriaYes
clarifying_questionsYes
input_aliases_appliedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond that: it discloses that gaps surface as unanswered criteria plus clarifying questions, that an opt-in private submission link is produced, and that no inventory is returned — behavior an agent would otherwise have to guess at.

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?

Audience tag and core action are front-loaded, and the long middle sentence is a deliberate enumeration of criteria rather than filler. The two closing clauses (opt-in link, no-inventory disclaimer) each earn their place. Slightly dense and comma-heavy, but nothing is redundant.

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 12-parameter tool with a nested object, the description covers the input surface conceptually and previews the outputs (unanswered criteria, clarifying questions, per-criterion fit results), and an output schema exists to carry return-value detail. The main remaining gap is that the nested portfolio profile is described only as "aggregate portfolio profile" without saying what it should contain.

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 0%, so the description carries the burden of explaining 12 parameters including a nested portfolio object. It helpfully maps the criteria groups (age bands, placement levels, minimum media, size range, excluded states, structure) to the inputs, but it does not explain formats, defaults, the min/max pair semantics, require_in_statute_min_pct, or the individual fields inside the aggregate portfolio profile.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific transformation: converts stated criteria (asset types, age bands, placement levels, min media, size range, excluded states, structure) into a structured buy box, then lists unanswered criteria and checks fit against a supplied portfolio. The output behaviors (clarifying questions, opt-in submission link) make the tool unambiguously distinct from siblings like portfolio_snapshot or sale_readiness_check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The "[buyers] For debt buyers" tag and the conditional "if you also pass an aggregate portfolio profile" clause give clear context for when the fit-check branch applies. It also rules out a key misreading with "No inventory is listed or implied." However, it never names an alternative tool or states an explicit when-not-to-use condition, so it stops short of full routing guidance.

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