Skip to main content
Glama

Don of Debt Portfolio Tools

Search Don of Debt FAQs

faq_search
Read-onlyIdempotent

[all] For every audience. Keyword search over the 229 published FAQ answers on donofdebt.com, optionally filtered to lender, agency, or buyer pages (default: all). Returns the questions and answers verbatim with their page links. Do not put personal or account details in the query.

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": {
      "query": "<query>"
    },
    "name": "faq_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
audienceNoFilter by the audience of the FAQ's page. Default all.

Output Schema

NameRequiredDescriptionDefault
roleYes
toolYes
as_ofYes
queryYes
corpusYes
noticeYes
resultsYes
sourcesYes
audienceYes
next_stepYes
disclaimerYes
educationalYes
result_countYes
audience_filterYes
input_aliases_appliedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, closed-world), so the description's added value is in disclosing the corpus size, that results are returned verbatim with page links, and a privacy constraint on query content. The one missing behavioral detail is what 'limit' caps and what happens to results beyond it.

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?

Four compact sentences with the audience scope front-loaded, and no filler. The leading '[all] For every audience.' tag is slightly awkward as an opener and duplicates the audience enum's default, but it costs little and the rest is dense and readable.

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 shape needn't be spelled out, and the description still usefully says answers come back verbatim with page links. Combined with annotations, an agent has nearly everything needed; only the meaning of 'limit' relative to the result set is unaddressed.

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 only 33% (only 'audience' is documented in the schema), so the description compensates by explaining that the search is keyword-based, that the filter is on the FAQ page's audience, and that the default is all pages. The 'limit' parameter (1-10) is left unexplained beyond its numeric bounds, which is the remaining gap.

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 verb and resource ('Keyword search over the 229 published FAQ answers on donofdebt.com') with scope quantified (229 answers) and the filterable dimension named (lender, agency, buyer pages). This is clearly distinguishable from sibling tools, which are checklists, calculators, and guides rather than a keyword search.

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?

Gives clear context for when the tool applies ('For every audience', with an optional audience filter and stated default of all) plus a hard constraint not to put personal or account details in the query. It stops short of explicit when-not-to-use guidance or naming an alternative for non-FAQ questions, so it falls just below the top band.

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