Skip to main content
Glama

AINDEX

Morpho Blue lending markets and vaults

list_morpho_markets
Read-only

Morpho Blue markets on Robinhood Chain: every market Morpho lists, and unlisted ones with real money. Loan and collateral tokens, LLTV, supply and borrow APY, utilisation, size, free liquidity, whether Morpho lists it (an unlisted market is for exits only), and AINDEX's review of it. Also Morpho's listed vaults with TVL and APY.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_morpho_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine context beyond that: it enumerates the returned data points (loan/collateral tokens, LLTV, APYs, utilisation, free liquidity), explains the listed/unlisted distinction and that unlisted markets are exit-only, and notes an AINDEX review field. It omits pagination, ordering, and whether results are bounded or complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Only two sentences, front-loaded with the resource and chain, with no filler. The first sentence is long and packs an enumerated field list, but that enumeration is doing real work in the absence of an output schema. Dense but justified.

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?

With no output schema, the description carries responsibility for telling the agent what comes back, and it delivers a concrete field inventory plus the semantic meaning of the listed flag. With zero parameters and read-only annotations, little else is required. Missing only response-shape details such as array size, ordering, or pagination.

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?

The tool takes zero parameters and the schema is an empty object, so there are no parameter semantics to document. The baseline of 4 applies; nothing in the description is needed here.

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 ('Morpho Blue markets on Robinhood Chain') and scopes it precisely to every listed market plus unlisted ones with real money, extending to Morpho's listed vaults. An agent knows exactly what data set this returns. It does not explicitly contrast itself with other listing tools (e.g. list_pools or get_lighter_markets), so it falls short of full sibling differentiation.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative. The one piece of actionable guidance is embedded in field documentation: an unlisted market 'is for exits only', which tells the agent how to interpret and act on that flag. Usage is otherwise implied by the listing nature of the tool.

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.

Resources