Skip to main content
Glama

Get one collateral token

get_market
Read-onlyIdempotent

Price, max loan-to-value, USDC available to borrow, active loans and pricing type for one 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": {
      "asset": "<asset>"
    },
    "name": "get_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYesToken contract address on Base (preferred) or its symbol, e.g. WETH, VIRTUAL, esALB

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds that the payload contains live borrowing state (USDC available, active loans), but says nothing about data freshness, chain/network assumptions beyond the schema, or failure behavior for an unknown symbol.

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?

A single sentence with zero filler, front-loading the returned fields. It is efficient, though it reads as a field list rather than stating an action verb like 'fetch' or 'retrieve', which slightly weakens the lead.

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?

There is no output schema, so the description carries the return-value burden and does discharge it by listing the five headline fields an agent gets back. For a one-parameter read-only lookup this is nearly sufficient; only freshness/unit semantics (e.g. how max LTV is expressed) are left unstated.

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%, and the asset property already documents 'contract address on Base (preferred) or its symbol' with examples. The description's 'for one token' adds no syntax, format, or resolution-order detail beyond what the schema provides, so the baseline 3 applies.

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?

The description names a specific resource ('one token') and enumerates exactly what is returned: price, max loan-to-value, USDC available to borrow, active loans, and pricing type. That is enough to distinguish it from list_markets (many tokens) or get_risk_report, though it never names those siblings explicitly.

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 only implied by the phrase 'for one token' – an agent can infer this is the single-asset lookup versus the list variant. There is no explicit when-to-use or when-not-to-use statement, and no routing toward get_risk_report or list_markets for adjacent needs.

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.