Gate Info MCP

info_platformmetrics_get_yield_pools

Read-onlyIdempotent

Lending and LP pools by APY or TVL. scope=full adds apy_base_30d, apy_reward_30d, reward_tokens, market_share. One protocol profile→get_platform_info. TVL series→get_platform_history. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.

Input Schema

TableJSON Schema

Name	Required	Description
`chain`	No	Chain filter.
`limit`	No	Rows; default 20, max 400.
`scope`	No	basic (default)\|full. full adds apy_base_30d, apy_reward_30d, reward_tokens, market_share.
`symbol`	No	Asset e.g. USDC, ETH-USDC.
`project`	No	Protocol e.g. aave-v3.
`sort_by`	No	apy\|tvl_usd; default apy.
`pool_type`	No	Exposure single\|multi or Lending\|LP\|Staking; maps to ES exposure.
`min_tvl_usd`	No	Min TVL USD; default 100000 when omitted; 0 = no floor.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	Yes
`count`	Yes
`items`	Yes
`limit`	Yes
`scope`	Yes
`total`	Yes
`symbol`	Yes
`project`	Yes
`sort_by`	Yes
`pool_type`	Yes
`duration_ms`	Yes
`min_tvl_usd`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedAug 27, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- changedInput schema / properties / min_tvl_usd / type
```
Previous value: -"number"New value: +[
+  "null",
+  "number"
+]
```
- addedOutput schema / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / items / items / additionalProperties
```
Added value: +true
```
- changedOutput schema / properties / items / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```

Changed3 schema fields changedJun 10, 2026

addedInput schema / properties / scope

Added value: +{
+  "description": "basic (default)|full. full adds apy_base_30d, apy_reward_30d, reward_tokens, market_share.",
+  "type": "string"
+}

addedOutput schema / properties / scope
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "project",
-  "chain",
-  "symbol",
-  "pool_type",
-  "sort_by",
-  "min_tvl_usd",
-  "limit",
-  "total",
-  "count",
-  "items",
-  "duration_ms"
-]New value: +[
+  "project",
+  "chain",
+  "symbol",
+  "pool_type",
+  "sort_by",
+  "min_tvl_usd",
+  "limit",
+  "scope",
+  "total",
+  "count",
+  "items",
+  "duration_ms"
+]

First observedApr 16, 2026

TDQS

B3.1/5.0

Behavior4/5

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

The description explicitly states 'Read-only public research data. No account access, no order placement or fund transfers', which aligns with the readOnlyHint annotation and adds context about data accessibility. This goes beyond the annotation's bare flag by clarifying that the tool is safe and non-destructive. No contradiction exists, so the score remains high.

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?

The description is brief but poorly structured. It mixes declarative statements with arrow notations and repeated scope hints, creating a fragmented flow. Phrases like 'scope=full adds apy_base_30d...' are placed awkwardly, and the arrows ('→') are unconventional. While concise, the lack of coherent structure undermines readability and comprehension.

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?

Given the tool has 8 optional parameters and no output schema details, a self-contained description is essential. The description references sibling tools via arrows ('get_platform_info', 'get_platform_history') without explaining their relevance, and it does not define key terms like 'exposure' or clarify how 'scope' affects results. A newcomer would struggle to fully understand the tool's capabilities from this text alone.

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%, with each parameter having a short description (e.g., 'Chain filter.', 'Rows; default 20, max 400.'). The tool description adds little beyond the schema, except a cryptic note that pool_type 'maps to ES exposure' which may confuse rather than clarify. Since the schema already carries most semantic weight, a baseline of 3 is appropriate; the description does not meaningfully enrich parameter understanding.

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 opens with 'Lending and LP pools by APY or TVL', which provides a clear verb (get) and resource (yield pools). It distinguishes the tool from siblings by its focus on yield/lending metrics, and the title 'Get Yield Pools' reinforces the purpose. However, the subsequent shorthand arrows (e.g., 'One protocol profile→get_platform_info') introduce ambiguity that slightly weakens clarity.

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?

No explicit guidance is given on when to use this tool versus alternatives. The description mentions 'One protocol profile→get_platform_info' and 'TVL series→get_platform_history', but these are cryptic references rather than clear conditional instructions. Users are left to infer that this tool is for current pool listings, not historical series, without any direct statement.

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

All Gate Info MCP tools Inspect

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.