Skip to main content
Glama
Sign In
DEX Pools MCP

DEX Pools MCP

by kukapay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_supported_networks

Retrieve a paginated list of supported networks from GeckoTerminal. Results displayed as a formatted table with network IDs and names.

Instructions

Query all supported networks on GeckoTerminal and return a formatted table.

Args:
    page: Page number for pagination (default: 1)

Returns:
    Formatted table as a string with columns: id, name

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

Input Schema

NameRequiredDescriptionDefault
pageNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description must cover behavior. It discloses pagination and return format (formatted string with columns), but lacks details on error handling, rate limits, or empty results. Adequate for a simple read query.

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?

The description is concise: two sentences plus an Args section, no fluff. Purpose and parameter are front-loaded, making it efficient for an AI agent to parse.

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?

Given the tool's simplicity (one optional param, output schema exists), the description covers the key points: what it returns (formatted table with columns) and pagination. It could mention page size or total pages, but overall it's sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description fully compensates. It explains the 'page' parameter as 'Page number for pagination (default: 1),' adding clear semantic meaning beyond the schema's type and default.

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 'Query all supported networks on GeckoTerminal and return a formatted table.' This is a specific verb-resource pair that distinguishes from sibling tools like get_supported_dexes_by_network, which focuses on exchanges by network.

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

Usage Guidelines4/5

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

The description implies usage: query all networks with optional pagination. It does not explicitly exclude other tools or state when-not, but the purpose is straightforward and distinct from siblings, so the context is clear.

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

Deploy Server

Other Tools