Skip to main content
Glama

Don of Debt Portfolio Tools

Request a private introduction (link only)

request_introduction
Read-only

[shared] Returns the link to The Don of Debt's private inquiry form and a random reference code you can paste into it. This tool never collects or submits contact details, and the reference code is not stored anywhere.

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

Input Schema

NameRequiredDescriptionDefault
sideNo

Output Schema

NameRequiredDescriptionDefault
roleYes
toolYes
as_ofYes
noticeYes
sourcesYes
audienceYes
next_stepYes
disclaimerYes
how_to_useYes
educationalYes
reference_codeYes
what_to_expectYes
inquiry_form_urlYes
site_page_with_formYes
input_aliases_appliedYes
reference_code_storedYes
collects_contact_detailsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, non-open-world behavior, but the description adds genuinely new context: no contact details are collected or submitted, and the reference code is not stored anywhere. This also explains the idempotentHint=false signal, since each call yields a fresh random code.

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 tight sentences with the primary output front-loaded and the trust/privacy caveat immediately after. The leading '[shared]' token is mildly opaque but costs little.

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 values need no prose, and the privacy note covers the main agent concern for a link-only tool. The one real gap is the undocumented `side` 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?

The single optional parameter `side` (enum seller/buyer/agency/lender/other) is never mentioned, and schema description coverage is 0%. The description does not say whether `side` changes the returned link, the code, or nothing at all, so the agent must guess about the only input.

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 concrete verb and concrete outputs: returns the link to a private inquiry form plus a random reference code. That is unmistakably different from the checklist/calculator siblings, but the description never names a sibling or clarifies overlap, 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?

It implies the workflow (get the link, paste the code into the form) but gives no explicit when-to-use condition, no prerequisites, and no exclusions. Usage is inferable 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