Skip to main content
Glama
Sign In
IndigoProtocol/indigo-mcp

IndigoProtocol/indigo-mcp

Official
by IndigoProtocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_steelswap_tokens

Retrieve the complete list of tokens listed on Steelswap DEX to identify available trading assets and support DEX-related queries.

Instructions

Get all tokens available on Steelswap DEX

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_steelswap_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.14

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention whether authentication is required, if the operation is idempotent, pagination behavior for 'all' tokens, or rate limits. The verb 'Get' implies a read operation but lacks explicit confirmation of safety or side effects.

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 a single, efficient sentence with no redundant words. It immediately communicates the resource and scope without filler content.

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?

Given the absence of an output schema and annotations, the description adequately identifies the resource scope (Steelswap DEX tokens) but leaves gaps regarding the return value structure (e.g., token metadata, addresses, symbols) and operational constraints. Sufficient for basic selection but incomplete for full invocation context.

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?

The input schema contains zero parameters. According to calibration rules, 0 params equals a baseline score of 4. The description appropriately does not invent parameters, maintaining alignment with the empty schema.

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 a clear verb ('Get') and specific resource ('all tokens available on Steelswap DEX'), identifying the exact domain. However, it does not explicitly differentiate from the sibling tool 'get_steelswap_estimate', which also involves Steelswap but returns different data.

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 states what the tool does but provides no guidance on when to use it versus alternatives (e.g., when to query Steelswap tokens versus general assets or other DEX data). No prerequisites, filtering guidance, or exclusions are mentioned.

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