Skip to main content
Glama

List collateral tokens

list_markets
Read-onlyIdempotent

Every token currently accepted as collateral, with price, max loan-to-value, USDC available to borrow against it, active loans, and how it is priced. Set only_with_funds to see only tokens lenders are currently backing.

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_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
only_with_fundsNoOnly tokens with USDC available to borrow right now

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 readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. What the description adds is genuinely useful: with no output schema, it enumerates the returned fields and notes that pricing method is included, which tells the agent what a response contains. It is silent on ordering, freshness, and whether the list is paginated.

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, no filler. The payload of the list is described first and the filter hint follows, so the most important information is front-loaded.

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 single-flag read tool with annotations covering its safety profile, this is close to sufficient: the description explains both the returned fields and the one filter. The remaining gap is contextual — no guidance on ordering or how results relate to get_market.

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 100% for the single boolean, so the schema already explains only_with_funds. The description restates it in lender-centric language ('tokens lenders are currently backing'), which nudges interpretation slightly but adds no syntax, defaults, or edge-case behavior beyond the schema text.

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 resource and verb: every token currently accepted as collateral, along with the exact fields returned (price, max LTV, USDC available, active loans, pricing method). The listing scope is unambiguous, though it never contrasts itself with adjacent reads like get_market or explain_collateral_types.

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 only conditional guidance is about the filter flag: 'set only_with_funds to see only tokens lenders are currently backing.' There is no explicit statement of when to call this versus get_market or explain_collateral_types, so selection between siblings is left to inference.

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.