Skip to main content
Glama

sodax_get_partners

Read-only

List all SODAX integration partners (wallets, DEXs, protocols). Filter by chain ID and select output format: JSON or markdown.

Instructions

List all SODAX integration partners including wallets, DEXs, and other protocols

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainIdNoFilter partners by numeric chain ID (e.g. 146 for Sonic)
formatNoResponse format: 'json' for raw data or 'markdown' for formatted textmarkdown
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description does not add any behavioral traits beyond what annotations provide (e.g., pagination, performance implications).

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?

Single sentence with 11 words, front-loaded with action. No fluff.

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 (no output schema, fully documented parameters), the description is sufficient for an agent to understand its purpose and scope.

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%, so schema fully documents parameters. The description adds no extra meaning to parameters beyond the schema. Baseline is 3.

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 action 'List' and resource 'SODAX integration partners' with examples (wallets, DEXs, other protocols). It distinguishes from sibling tools like sodax_get_partner_summary.

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 (e.g., sodax_get_partner_summary) or any context about when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gosodax/builders-sodax-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server