Skip to main content
Glama

Prepare a collateral claim

build_claim_collateral
Read-onlyIdempotent

Returns the unsigned transaction for a lender to claim their share of collateral from loans that passed their due date without a full buyback.

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": {
      "loan_ids": "<loan_ids>"
    },
    "name": "build_claim_collateral"
  }
}

Input Schema

NameRequiredDescriptionDefault
loan_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds genuinely useful behavior beyond that: the output is an *unsigned* transaction, meaning the claim is prepared, not executed, and eligibility is limited to defaulted loans without a full buyback. It does not state what happens when a supplied loan is ineligible (revert, skip, or partial result).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the action verb first and the qualifying condition last; no redundant restatement of the name or title.

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 one-parameter transaction-builder with annotations covering safety and no output schema, the description covers what the tool produces (an unsigned tx) and who it is for (the lender). The main residual gap is error/partial-eligibility behavior for the loan_ids batch.

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% for the single parameter loan_ids, so the description carries the full burden and does not compensate. The plural 'loans' loosely implies batching, but nothing explains the 1–50 element bound, the string-vs-integer ID forms, or how mixed-eligibility batches are handled.

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 gives a specific verb and artifact ('Returns the unsigned transaction'), a named resource ('their share of collateral'), and the eligibility condition ('loans that passed their due date without a full buyback'). It implicitly separates this from build_claim_proceeds via the collateral-vs-proceeds distinction, but never names the sibling or states the contrast explicitly.

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 precondition 'loans that passed their due date without a full buyback' effectively tells the agent when this tool applies. There is no explicit exclusion or named alternative (e.g., what to use for repaid loans), so the guidance stops short of full routing.

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.