Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

defi_yield_tvl_stablecoin_monitor

Read-onlyIdempotent

DeFi Yield TVL & Stablecoin Monitor API: Live DeFi liquidity pool APY, TVL, and stablecoin risk analytics across Ethereum, Solana, Arbitrum, and Base.

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": "defi_yield_tvl_stablecoin_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoBlockchain filter (e.g., "Ethereum", "Arbitrum", "Base", "ALL").Ethereum
limitNoMaximum pool records to return (1-50, default: 10).
queryNoToken or protocol filter (e.g., "USDC", "ETH", "AAVE").USDC
minTvlNoMinimum Total Value Locked in USD (default: 100000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / chain
      Added value: +{
      +  "default": "Ethereum",
      +  "description": "Blockchain filter (e.g., \"Ethereum\", \"Arbitrum\", \"Base\", \"ALL\").",
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 10,
      +  "description": "Maximum pool records to return (1-50, default: 10).",
      +  "type": "integer"
      +}
    • removedInput schema / properties / maxResults
      Removed value: -{
      -  "default": 10,
      -  "description": "Maximum number of structured items to extract.",
      -  "type": "integer"
      -}
    • addedInput schema / properties / minTvl
      Added value: +{
      +  "default": 100000,
      +  "description": "Minimum Total Value Locked in USD (default: 100000).",
      +  "type": "integer"
      +}
    • addedInput schema / properties / query
      Added value: +{
      +  "default": "USDC",
      +  "description": "Token or protocol filter (e.g., \"USDC\", \"ETH\", \"AAVE\").",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered by structured data. The description adds the supported chain set (Ethereum, Solana, Arbitrum, Base), which is genuinely useful context not expressed as an enum in the schema. It says nothing about data freshness/latency, rate limits, or whether stablecoin risk scores are third-party sourced — gaps that matter for an open-world live-data tool.

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?

It is a single front-loaded sentence with no filler clauses or hedging, so nothing needs trimming. The tradeoff is low information density: nearly every phrase restates the tool name and title rather than adding new operational content. Efficient in form, thin in payload.

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?

For a four-parameter, open-world, read-only market data tool with no output schema, the description does not indicate what a record contains, whether results are sorted by TVL or APY, or how 'stablecoin risk analytics' is surfaced. Annotations cover safety but not data shape, so the description leaves real ambiguity about what the agent will receive. It is adequate as an identity statement but incomplete as a usage contract.

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 all four parameters (chain, limit, query, minTvl) are already documented with defaults and examples, making 3 the baseline. The description's chain list adds marginal value by confirming Solana is in scope even though the schema example enumerates only Ethereum/Arbitrum/Base/ALL. No additional semantics such as sort order or how query matches protocol vs token are supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource domain — DeFi liquidity pool APY, TVL, and stablecoin risk analytics across four named chains — so an agent can tell roughly what data comes back. However, it reads as a product tagline rather than a verb-plus-resource statement, and it offers no differentiation from siblings like crypto_orderbook_arbitrage_scanner or dex_token_scanner_security_auditor. The purpose is inferable but not crisply defined.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no named alternative. The agent must infer from the tagline alone whether this is the right tool for cross-chain pool screening versus token security or orderbook scanning. Scope words like 'live' hint at real-time screening but never state the trigger condition for choosing this 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