Skip to main content
Glama
Sign In

GMPSignal Real-Time Intelligence MCP

by io.github.xpayrcom
OverviewDiscussionsAdmin

defi_yield_tvl_stablecoin_monitor

DeFi Yield Farming, Protocol TVL & Stablecoin Monitor: Real-time structured data extraction feed for DeFi Yield Farming, Protocol TVL & Stablecoin Monitor.

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
maxResultsNoMaximum number of structured items to extract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing about data sources, refresh cadence beyond the word 'real-time', rate limits, or coverage. 'Real-time structured data extraction feed' is not a behavior disclosure an agent can act on.

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

Conciseness2/5

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

Two sentences where the second is a near-verbatim repetition of the first with 'structured data extraction feed' appended. It is short but redundant rather than front-loaded with useful information.

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?

The tool is simple (one optional param, no output schema), yet an agent still cannot tell what data comes back or what distinguishes a 'protocol TVL' result from a 'stablecoin' result. With no annotations and no output schema, the description should have covered return shape and scope and does not.

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?

There is a single optional parameter, maxResults, and the schema documents it at 100 percent coverage with a clear description, so the schema already does the work. The description adds no meaning beyond it; baseline 3 applies.

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

Purpose2/5

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

The description names the data domains (DeFi yield farming, protocol TVL, stablecoins) but the only verb phrase is 'Real-time structured data extraction feed,' which simply restates that it is a feed. It does not say what the tool actually does differently from sibling monitors such as crypto_orderbook_arbitrage_scanner or dex_token_scanner_security_auditor.

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

Usage Guidelines1/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 is left to guess whether this is for yield APY discovery, TVL tracking, or stablecoin peg monitoring.

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

All GMPSignal Real-Time Intelligence MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources