Skip to main content
Glama
GMPSignal MCP Server

GMPSignal MCP Server

monitor_defi_yield_and_tvl

Read-onlyIdempotent

Query live DeFi yield pool APYs, protocol TVL momentum, and stablecoin peg deviations across chains to assess farming opportunities and protocol risk.

Instructions

Monitor decentralized finance (DeFi) yield farming APY pools, multi-chain protocol Total Value Locked (TVL) momentum, and stablecoin peg deviations using live DeFiLlama intelligence.

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": {
      "mode": "<mode>"
    },
    "name": "monitor_defi_yield_and_tvl"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesDataset view to query: yield_pools (APY rankings), protocol_tvl (protocol TVL flows), or stablecoins (peg health).yield_pools
chainsNoBlockchain ecosystems to include in the DeFi scan.
minTvlUsdNoMinimum pool or protocol TVL in USD.
maxResultsNoMaximum number of DeFi records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

TDQS

B3.4/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. The description adds that it uses live DeFiLlama intelligence, but does not disclose freshness, rate limits, or return behavior.

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?

It is a single front-loaded sentence that names the action and all three monitored domains without filler. The parenthetical expansions are helpful rather than redundant.

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 read-only monitoring tool with full parameter descriptions and annotations, the definition is mostly complete. It names the analytical domains and data source, though without an output schema it does not describe return format or freshness in detail.

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 all four parameters. The description restates the three dataset views but adds no parameter syntax, defaults, or constraints beyond what the schema provides.

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 monitoring verb and names three concrete DeFi resources: yield farming APY pools, protocol TVL momentum, and stablecoin peg deviations, plus the data source DeFiLlama. It does not explicitly distinguish itself from nearby crypto siblings, but the scope is clear.

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?

The description implies that it is used to monitor DeFi metrics, but it does not say when to choose this tool over alternatives or when not to use it. The mode values are described in the schema rather than as usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.