Skip to main content
Glama
Sign In
Sera MCP Server

Sera MCP Server

Official
by sera-cx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_trading_pairs

Find all available trading pairs for a specific token, showing every market where it can be swapped.

Instructions

Get available trading pairs/markets for a specific token. Returns all pairs where the token can be swapped.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token_address": "<token_address>"
    },
    "name": "get_trading_pairs"
  }
}

Input Schema

NameRequiredDescriptionDefault
token_addressYesToken contract address to find trading pairs for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It states it returns all pairs where token can be swapped, which is a clear read behavior, but it does not disclose auth requirements, pagination, or any side effects. This is minimal but not misleading.

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 two short sentences, both necessary and informative. It states the core action and the result, with no unnecessary words or repetition.

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

Completeness3/5

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

There is no output schema, so the description must explain the return value. It conceptually does ('Returns all pairs where the token can be swapped') but lacks details on response structure, market status, pagination, or limitations. This is adequate but not fully complete.

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% for token_address, so the schema already explains the parameter. The description does not add any extra semantics about parameters, so a baseline score of 3 is appropriate.

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 uses the specific verb 'Get' and resource 'trading pairs/markets for a specific token', clearly indicating it returns swap pairs for a token. It does not explicitly distinguish from sibling tool 'get_market', but the scope of 'all pairs where the token can be swapped' helps clarify its purpose.

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?

The description provides no guidance on when to use this tool versus alternatives, no mention of exclusions or prerequisites. The usage context is implied rather than explicit.

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