Skip to main content
Glama

getNetworkDexes

Read-onlyIdempotent

List the DEXes (exchanges) operating on one network, such as Uniswap on ethereum or Raydium on solana, returned under 'dexes' with page_info (page, total_pages). Read-only and keyless. Use for 'which DEXes are on Base?', 'does Solana have Orca?', or to get a dex id to feed into getDexPools. Scope is a single network; call getNetworks first for the slug. Params: network (required slug); limit (default 10, max 100); page (default 1, 1-indexed); sort_by (only 'pool'; legacy alias order_by); sort_dir 'asc' or 'desc' (default 'desc'; legacy alias sort).

Input Schema

NameRequiredDescriptionDefault
pageNoOPTIONAL: Page number, 1-indexed. Server accepts page=0 (treated as page=1) for backward compatibility.
sortNoOPTIONAL: alias of sort_dir; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes sort, so use this name when calling the REST API directly.
limitNoOPTIONAL: Number of items per page (default: 10, max: 100)
networkYesREQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
sort_byNoOPTIONAL: Sort field. Canonical parameter name; older tools used order_by. The REST API calls this parameter order_by.
order_byNoOPTIONAL: alias of sort_by; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes order_by, so use this name when calling the REST API directly.
sort_dirNoOPTIONAL: Sort direction (asc/desc). Canonical parameter name. Defaults to 'desc' if neither sort_dir nor sort is provided. The REST API calls this parameter sort.
rationaleYesREQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions` field for the full convention and worked examples.

Output Schema

NameRequiredDescriptionDefault
dexesYes
page_infoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedOutput schema / properties / dexes / items / additionalProperties
      Removed value: -true
    • addedOutput schema / properties / dexes / items / anyOf
      Added value: +[
      +  {
      +    "additionalProperties": true,
      +    "properties": {
      +      "chain": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "dex_id": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "dex_name": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "display_name": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "id": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "network_id": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "pools_count": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "protocol": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "txns_24h": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "volume_usd_24h": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / dexes / items / properties
      Removed value: -{
      -  "chain": {
      -    "type": "string"
      -  },
      -  "dex_id": {
      -    "type": "string"
      -  },
      -  "dex_name": {
      -    "type": "string"
      -  },
      -  "display_name": {
      -    "type": "string"
      -  },
      -  "id": {
      -    "type": "string"
      -  },
      -  "network_id": {
      -    "type": "string"
      -  },
      -  "pools_count": {
      -    "type": "number"
      -  },
      -  "protocol": {
      -    "type": "string"
      -  },
      -  "txns_24h": {
      -    "type": "number"
      -  },
      -  "volume_usd_24h": {
      -    "type": "number"
      -  }
      -}
    • removedOutput schema / properties / dexes / items / type
      Removed value: -"object"
    • removedOutput schema / properties / page_info / additionalProperties
      Removed value: -true
    • addedOutput schema / properties / page_info / anyOf
      Added value: +[
      +  {
      +    "additionalProperties": true,
      +    "properties": {
      +      "limit": {
      +        "description": "Items per page in the request.",
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "page": {
      +        "description": "Current page number (1-indexed).",
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "total_items": {
      +        "description": "Total number of items across all pages.",
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "total_pages": {
      +        "description": "Total number of pages available.",
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / page_info / properties
      Removed value: -{
      -  "limit": {
      -    "description": "Items per page in the request.",
      -    "type": "number"
      -  },
      -  "page": {
      -    "description": "Current page number (1-indexed).",
      -    "type": "number"
      -  },
      -  "total_items": {
      -    "description": "Total number of items across all pages.",
      -    "type": "number"
      -  },
      -  "total_pages": {
      -    "description": "Total number of pages available.",
      -    "type": "number"
      -  }
      -}
    • removedOutput schema / properties / page_info / type
      Removed value: -"object"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "dexes": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "chain": {
      +            "type": "string"
      +          },
      +          "dex_id": {
      +            "type": "string"
      +          },
      +          "dex_name": {
      +            "type": "string"
      +          },
      +          "display_name": {
      +            "type": "string"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "network_id": {
      +            "type": "string"
      +          },
      +          "pools_count": {
      +            "type": "number"
      +          },
      +          "protocol": {
      +            "type": "string"
      +          },
      +          "txns_24h": {
      +            "type": "number"
      +          },
      +          "volume_usd_24h": {
      +            "type": "number"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "page_info": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "limit": {
      +          "description": "Items per page in the request.",
      +          "type": "number"
      +        },
      +        "page": {
      +          "description": "Current page number (1-indexed).",
      +          "type": "number"
      +        },
      +        "total_items": {
      +          "description": "Total number of items across all pages.",
      +          "type": "number"
      +        },
      +        "total_pages": {
      +          "description": "Total number of pages available.",
      +          "type": "number"
      +        }
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "dexes",
      +    "page_info"
      +  ],
      +  "type": "object"
      +}
  3. Changed4 schema fields changed
    • changedInput schema / properties / order_by / description
      Previous value: -"DEPRECATED alias for sort_by. Both accepted; prefer sort_by going forward."New value: +"OPTIONAL: alias of sort_by; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes order_by, so use this name when calling the REST API directly."
    • changedInput schema / properties / sort / description
      Previous value: -"DEPRECATED alias for sort_dir. Both accepted; prefer sort_dir going forward."New value: +"OPTIONAL: alias of sort_dir; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes sort, so use this name when calling the REST API directly."
    • changedInput schema / properties / sort_by / description
      Previous value: -"OPTIONAL: Sort field. Canonical parameter name; older tools used order_by."New value: +"OPTIONAL: Sort field. Canonical parameter name; older tools used order_by. The REST API calls this parameter order_by."
    • changedInput schema / properties / sort_dir / description
      Previous value: -"OPTIONAL: Sort direction (asc/desc). Canonical parameter name. Defaults to 'desc' if neither sort_dir nor sort is provided."New value: +"OPTIONAL: Sort direction (asc/desc). Canonical parameter name. Defaults to 'desc' if neither sort_dir nor sort is provided. The REST API calls this parameter sort."
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds genuinely new context beyond that: 'keyless' auth and the response envelope ('dexes' plus page_info with page and total_pages), which tells the agent pagination exists. It does not discuss rate limits or ordering guarantees, keeping it short of a 5.

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?

Front-loaded with purpose and return shape, then use cases, then scope warning, then params — a sensible ordering. It is a single dense paragraph with some redundancy in restating all parameter defaults, but no sentence is filler.

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?

With an output schema present, the description needn't detail return values, and it still sketches the envelope. Ranges, defaults, alias handling, prerequisites and downstream usage are all covered; only the mandatory rationale convention is left to the server instructions field.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description nonetheless consolidates the parameters with defaults and ranges (limit default 10 max 100, page 1-indexed, sort_by only 'pool', sort_dir default 'desc') and flags the legacy aliases order_by/sort, which helps an agent avoid the alias trap. The required 'rationale' parameter is not mentioned, which is the only gap.

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?

Names a specific verb and resource ('List the DEXes operating on one network') and immediately grounds it with concrete examples (Uniswap on ethereum, Raydium on solana). It also distinguishes itself from siblings by scoping to a single network and pointing to getDexPools for the follow-on step.

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?

Explicit usage contexts are given as quoted user questions ('which DEXes are on Base?', 'does Solana have Orca?') plus a stated precondition ('call getNetworks first for the slug') and an explicit downstream consumer (getDexPools). Scope limit is stated as 'single network', which excludes the wrong calls.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources