Skip to main content
Glama
Sign In
lends-mcp-server

lends-mcp-server

Official
by LendsProtocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Lends Quote Psm Swap Out

lends_quote_psm_swap_out
Read-onlyIdempotent

Quote leUSD-to-USDG PSM conversion rates and check current swap availability.

Instructions

Quote exact leUSD-to-USDG PSM conversion and current availability.

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": {
      "leusdAmount": "<leusdAmount>"
    },
    "name": "lends_quote_psm_swap_out"
  }
}

Input Schema

NameRequiredDescriptionDefault
leusdAmountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds that the quote is 'exact' and reflects 'current availability', which is useful, but it does not go beyond that into return shape or potential edge cases.

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 short, front-loaded sentence with no filler. It packs the verb, resource, direction, and key output quality ('exact', 'current availability') into minimal words.

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 simple, read-only, one-parameter quote tool, the description is largely sufficient, especially with annotations covering safety and idempotency. There is no output schema, and the description gives a high-level sense of the return ('exact conversion and current availability') but not a precise return structure.

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?

With 0% schema description coverage, the description should explain the leusdAmount parameter, but it only implies it through 'leUSD-to-USDG PSM conversion'. The name and pattern are self-explanatory to a degree, but units, precision, and how the amount feeds the quote are not addressed.

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 uses a specific verb ('Quote') and a specific resource ('leUSD-to-USDG PSM conversion'), and it names the direction explicitly, which distinguishes it from lends_quote_psm_swap_in and the prepare_psm_swap_* tools. It also states what the caller gets back: an exact conversion and current availability.

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 directionality 'leUSD-to-USDG' makes it clear this is the swap-out quote rather than the swap-in quote, providing clear context for selection. It does not explicitly name alternatives or state exclusions, but the purpose is specific enough to route an agent correctly among the sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools