Skip to main content
Glama

Prepare auto re-lend setting

build_set_auto_redeploy
Read-onlyIdempotent

Returns the unsigned transaction to turn automatic re-lending of repaid principal on or off.

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": {
      "enabled": "<enabled>"
    },
    "name": "build_set_auto_redeploy"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description usefully adds that the output is an unsigned transaction rather than a completed state change. It still omits what the caller must do next (sign and broadcast) and any auth or chain requirements.

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?

One sentence, front-loaded with the return type and the effect, with no filler. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter transaction-builder with no output schema, the definition covers the what but not the workflow. An agent is left to infer that the returned unsigned transaction must be signed and submitted, which is the key next step for this tool family.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single 'enabled' parameter, but the description compensates by explaining the flag as turning automatic re-lending of repaid principal on or off. That is adequate, though it does not clarify the default state or what happens to already-accrued positions.

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 names a specific verb and resource: it returns an unsigned transaction that flips automatic re-lending of repaid principal. That is concrete and distinguishable from the get_* and quote_* siblings, though it does not explicitly contrast with the other build_* tools.

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?

Usage is only implied by the name and the 'returns the unsigned transaction' phrasing. There is no explicit statement of when to prefer this over simulate_transaction or the read-only getters, and no mention of prerequisites such as an existing loan or a connected wallet.

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.