Skip to main content
Glama

Don of Debt Portfolio Tools

Data tape header check (column names only)

data_tape_header_check
Read-onlyIdempotent

[lenders] Send ONLY the column header names of a data tape (no rows, no values). Maps each header to a standard field category, lists recommended fields that are missing (from the Don of Debt data tape checklist and Reg F itemization context), and flags columns holding sensitive personal data that should not be shared before an NDA and secure transfer.

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": {
      "columns": "<columns>"
    },
    "name": "data_tape_header_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
columnsYesHeader names only, e.g. ["acct_ref","chargeoff_date","chargeoff_balance","state"]

Output Schema

NameRequiredDescriptionDefault
roleYes
toolYes
as_ofYes
mappedYes
noticeYes
sourcesYes
audienceYes
boundaryYes
unmappedYes
next_stepYes
disclaimerYes
educationalYes
reconcile_firstYes
columns_receivedYes
sensitive_columnsYes
input_aliases_appliedYes
recommended_fields_missingYes

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 declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered; the description adds the substantive behavior instead — three concrete outputs (category mapping, missing-field list, PII flagging) and the provenance of the checklist ('Don of Debt data tape checklist and Reg F itemization context'). It does not say how unrecognized headers or low-confidence matches are reported, which is the only remaining behavioral gap.

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 most important constraint (headers only, no data) before describing the three outputs. The parenthetical sourcing of the checklist is dense but earns its place by telling the agent which standard drives the 'missing fields' list.

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 the description need not explain return values, and annotations cover the safety profile; what remains is input constraint plus analytical scope, both stated. The only omission is edge-case behavior on unmatched headers, which is a minor gap for a single-parameter read-only tool.

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 coverage is 100% and the single parameter carries its own example, so the schema does the heavy lifting. The description still adds real meaning by insisting the array contains header names only — no rows, no values — which is a semantic constraint on the content of the strings, not just their type.

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?

The description names a specific verb and resource ('maps each header to a standard field category', 'lists recommended fields that are missing', 'flags columns holding sensitive personal data') and draws a hard scope boundary with 'Send ONLY the column header names of a data tape (no rows, no values)'. No sibling tool in the catalog touches data-tape headers, so this is unambiguous even without naming an alternative.

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 description establishes the condition that selects this tool: a pre-NDA / pre-secure-transfer situation where only column names can be shared. It does not explicitly say when a different tool or a full data-tape review is more appropriate, but the input constraint makes the applicable context clear.

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