Skip to main content
Glama

sodax_get_partners

Read-only

Retrieve a list of SODAX integration partners including wallets, DEXs, and protocols to identify available ecosystem connections for development.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoResponse format: 'json' for raw data or 'markdown' for formatted textmarkdown

Implementation Reference

  • The actual implementation of getPartners() that fetches SODAX integration partners from the API. Uses caching and makes a GET request to /partners endpoint, returning an array of Partner objects.
    /**
     * List SODAX integration partners
     */
    export async function getPartners(): Promise<Partner[]> {
      const cacheKey = "partners";
      const cached = getCached<Partner[]>(cacheKey);
      if (cached) return cached;
    
      try {
        const response = await apiClient.get("/partners");
        const partners = response.data?.data || response.data || [];
        setCache(cacheKey, partners);
        return partners;
      } catch (error) {
        console.error("Error fetching partners:", error);
        throw new Error("Failed to fetch partners from SODAX API");
      }
    }
  • MCP tool registration for sodax_get_partners. Defines the tool schema with an optional format parameter (json/markdown), and wraps the getPartners() handler with error handling and response formatting.
    // Tool 9: Get Partners
    server.tool(
      "sodax_get_partners",
      "List all SODAX integration partners including wallets, DEXs, and other protocols",
      {
        format: z.nativeEnum(ResponseFormat).optional().default(ResponseFormat.MARKDOWN)
          .describe("Response format: 'json' for raw data or 'markdown' for formatted text")
      },
      READ_ONLY,
      async ({ format }) => {
        try {
          const partners = await getPartners();
          return {
            content: [{
              type: "text",
              text: `## SODAX Partners\n\n${partners.length} integration partners\n\n` + formatResponse(partners, format)
            }]
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error: ${error instanceof Error ? error.message : "Unknown error"}` }],
            isError: true
          };
        }
      }
    );
  • Type definition for the Partner interface representing SODAX integration partners with fields like id, name, type (wallet/dex/bridge/etc.), description, website, logoUrl, and supported chains.
    /**
     * Integration partner
     */
    export interface Partner {
      id: string;
      name: string;
      type: "wallet" | "dex" | "bridge" | "aggregator" | "lending" | "other";
      description?: string;
      website?: string;
      logoUrl?: string;
      chains?: string[];
    }
  • Analytics configuration mapping sodax_get_partners to the 'api' tool group for PostHog tracking and monitoring of tool usage.
    sodax_get_partners: "api",
  • src/index.ts:202-202 (registration)
    Lists sodax_get_partners in the API tools array exposed by the server's /api endpoint for documentation and discovery.
    "sodax_get_partners",
Behavior4/5

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

Annotations provide readOnlyHint=true, openWorldHint=true, and destructiveHint=false, indicating a safe, read-only operation with potentially dynamic data. The description adds value by specifying the types of partners included (wallets, DEXs, protocols), which is not covered by annotations. It doesn't contradict annotations and provides useful context beyond them.

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 that front-loads the key action ('List all SODAX integration partners') and includes essential details without redundancy. Every word earns its place, making it highly concise and well-structured for quick understanding.

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 low complexity (1 optional parameter), rich annotations covering safety and data nature, and no output schema, the description is mostly complete. It specifies what data is returned (partners including wallets, DEXs, protocols), but could benefit from mentioning the response structure or any limitations. However, it adequately supports the agent's understanding for this simple tool.

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%, with the 'format' parameter fully documented in the schema. The description does not add any parameter-specific information beyond what the schema provides, such as default behavior or usage tips. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to.

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 verb 'List' and the resource 'all SODAX integration partners', specifying the scope to include 'wallets, DEXs, and other protocols'. It distinguishes itself from siblings like 'sodax_get_supported_chains' or 'sodax_get_swap_tokens' by focusing on partners rather than chains, tokens, or other data types.

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

Usage Guidelines3/5

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

The description implies usage for retrieving partner information but does not explicitly state when to use this tool versus alternatives. For example, it doesn't clarify if this should be used over other tools for partner-related queries or specify any prerequisites. The context is clear but lacks explicit guidance on exclusions or comparisons.

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/sodax-builders-mcp'

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