Skip to main content
Glama
agenthill

recon-crypto-mcp

by agenthill
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

prepare_morpho_borrow

DestructiveIdempotent

Build an unsigned borrow transaction on Morpho Blue using pre-existing collateral to borrow assets from a specified market.

Instructions

Build an unsigned Morpho Blue borrow transaction. Requires pre-existing collateral in the market.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletYes0x-prefixed EVM wallet address (40 hex chars) that will execute this action.
chainNoEVM chain Morpho Blue is deployed on. Currently only ethereum is enabled.ethereum
marketIdYesMorpho Blue market id — 32-byte hex (0x + 64 hex chars). Identifies the market's (loanToken, collateralToken, oracle, irm, lltv) tuple. Discover via get_morpho_positions.
amountYesHuman-readable decimal amount, NOT raw wei/base units. Example: "10" for 10 USDC. Pass "max" for full-balance withdraw/repay.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.14.4
  2. Removed
  3. First observedv0.3.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations include destructiveHint=true and readOnlyHint=false, which are consistent. The description adds the precondition of collateral and clarifies it builds an unsigned transaction. No contradictions.

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?

Single sentence, front-loaded with the verb and resource. No extraneous words. Efficiently conveys the core purpose.

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

Completeness2/5

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

No output schema exists, yet the description does not specify what the tool returns (e.g., an unsigned transaction object). Given the tool's complexity and no output schema, this is a notable gap.

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 100%, so the schema already documents parameters well. The tool-level description does not add extra parameter meaning beyond what is in the schema, meeting the baseline for high coverage.

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 clearly states the action ('Build'), the resource ('unsigned Morpho Blue borrow transaction'), and includes a key precondition ('Requires pre-existing collateral'). This distinguishes it from sibling tools like prepare_morpho_supply or prepare_morpho_repay.

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?

The description implies usage when borrowing with existing collateral, but provides no explicit when-not-to-use guidance or alternatives. Sibling tools like prepare_morpho_repay exist, but no comparison is made.

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