Skip to main content
Glama

Prepare a proceeds claim

build_claim_proceeds
Read-onlyIdempotent

Returns the unsigned transaction to claim repaid USDC from loans you funded (mode withdraw) or put it straight back into lending (mode redeploy). Get loan IDs from get_lender_position.

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_proceeds"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
loan_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The description adds genuinely useful context beyond annotations by making clear the output is an unsigned transaction, so the caller still has to sign and submit it, and by explaining that mode redeploy re-enters the position rather than paying out. With readOnlyHint=true and idempotentHint=true already covering the safety profile, the remaining gap is that it doesn't say what happens if a loan has nothing to claim or how the returned transaction is meant to be consumed.

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?

Two tight sentences: the outcome and both modes come first, and the prerequisite pointer to get_lender_position follows. No filler or restatement of the 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 two-parameter transaction-builder with no output schema, the definition covers the important ground: what is built, what the modes mean, and where inputs come from. It leaves open the lifecycle around the returned transaction (signing/submission) and any failure conditions, which keeps it just short of complete.

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 0%, so the description carries the burden, and it largely does: it defines both enum values of mode in behavioral terms and identifies where loan_ids come from. It does not mention the 50-item cap, the numeric-string ID format, or that loan_ids is required, so some schema-level detail is left to the schema alone.

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 specific verb and resource: returns an unsigned transaction that claims repaid USDC from loans the caller funded, with the two modes spelled out. It is clearly distinguishable from build_claim_collateral by naming USDC proceeds rather than collateral, though it never names that sibling 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?

Gives concrete routing guidance by telling the agent to obtain loan IDs from get_lender_position, and explains which mode to pick for each outcome (cash out vs. re-lend). It stops short of stating prerequisites such as the loan needing to be in a repaid state or when this tool should not be used.

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.