Skip to main content
Glama

Prepare per-token lending limits

build_set_limits
Read-onlyIdempotent

Returns the unsigned transaction to add, change or remove per-token lending limits. A limit cannot be set below what is already in active loans for that token.

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": {
      "limits": "<limits>",
      "lender": "<lender>"
    },
    "name": "build_set_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
lenderYes
limitsYes

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?

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description correctly aligns by describing a transaction-builder rather than an executed write. It adds genuine context beyond the annotations: the output is an unsigned transaction, and an invariant (cannot set below existing active loans) governs whether the call will succeed. It stops short of stating how the transaction is submitted or how failures surface.

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 sentences, zero filler. The core action is front-loaded and the constraint follows as a qualifier, which is exactly the right ordering for an agent scanning for capability first.

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?

There is no output schema, and the description only says it returns an unsigned transaction without describing its shape or the next step (signing/submission). For a two-parameter builder tool this is workable but leaves the post-call workflow underspecified.

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 coverage is reported at 0% for top-level parameters, so the description carries weight; it clarifies that limits are per-token and that a limit value of 0 removes the entry (though that detail lives in the schema). The 'lender' parameter is never explained in the description, leaving a required address argument undocumented beyond its regex pattern.

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 the unsigned transaction to add, change or remove per-token lending limits.' The 'build_' naming convention and the 'unsigned transaction' framing place it clearly among the sibling build_* tools. It does not explicitly contrast with any sibling, which keeps it from 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?

Usage is implied by the resource: an agent would call this to set, modify, or clear a per-token limit. The constraint that a limit cannot go below active loans is a useful precondition, but there is no statement of when to prefer this over alternatives such as simulate_transaction first, or what to do with the returned transaction afterward.

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.