Gate Info MCP

info_platformmetrics_get_defi_overview

Read-onlyIdempotent

Cross-sector dashboard for DeFi, spot, perp, stablecoin, or bridge categories. One bridge ranking or chain detail→get_bridge_metrics. One protocol→get_platform_info. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`category`	No	all\|defi\|spot\|perp\|stablecoin\|bridge or platform type; unknown values passed through; empty if no match.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`items`	Yes
`total`	Yes
`category`	Yes
`duration_ms`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedAug 27, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- 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"
+]
```
First observedApr 16, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description adds behavioral transparency beyond the annotations by stating 'Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.' This clarifies safety and side-effect behavior consistent with readOnlyHint.

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?

The description is concise and front-loaded with the main purpose. It includes necessary routing and safety information, though the multiple short sentences could be consolidated slightly without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple interface with one optional parameter and an existing output schema, the description provides complete context: purpose, usage, routing, and safety. Nothing critical is missing for an agent to decide when and how to invoke this tool.

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?

The schema has 100% coverage for the single 'category' parameter with a detailed description of allowed values and handling of unknown inputs. The tool description does not add additional parameter semantics beyond the schema, so the baseline score of 3 applies.

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

Purpose5/5

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

The description clearly states the tool provides a cross-sector dashboard for DeFi, spot, perp, stablecoin, or bridge categories. It also distinguishes from sibling tools by specifying when to use get_bridge_metrics and get_platform_info, making the purpose unambiguous.

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

Usage Guidelines5/5

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

It explicitly provides routing guidelines: 'One bridge ranking or chain detail→get_bridge_metrics. One protocol→get_platform_info.' This tells the agent when to use alternative tools instead, satisfying the usage guidance requirement.

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.