Skip to main content
Glama

sodax_get_partner_summary

Read-only

Summarize volume and activity for a partner based on receiver address. Supports filtering by chain ID and format selection.

Instructions

Get volume and activity summary for a specific integration partner by their receiver address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
receiverYesThe partner receiver address
chainIdNoFilter by chain ID
formatNoResponse format: 'json' for raw data or 'markdown' for formatted textmarkdown

Implementation Reference

  • The actual API handler that fetches partner summary from /partners/:receiver/summary endpoint. Returns null on 404, otherwise throws on error.
    export async function getPartnerSummary(receiver: string, chainId?: string): Promise<unknown> {
      try {
        const params = new URLSearchParams();
        if (chainId) params.append("chainId", chainId);
    
        const queryString = params.toString();
        const url = `/partners/${receiver}/summary${queryString ? `?${queryString}` : ""}`;
        const response = await apiClient.get(url);
        return response.data;
      } catch (error) {
        if (axios.isAxiosError(error) && error.response?.status === 404) {
          return null;
        }
        console.error("Error fetching partner summary:", error);
        throw new Error("Failed to fetch partner summary from SODAX API");
      }
    }
  • MCP tool registration for 'sodax_get_partner_summary'. Defines the tool schema (receiver, chainId, format) and calls getPartnerSummary service, then formats the response as markdown.
    // Tool 25: Get Partner Summary
    server.tool(
      "sodax_get_partner_summary",
      "Get volume and activity summary for a specific integration partner by their receiver address",
      {
        receiver: z.string()
          .describe("The partner receiver address"),
        chainId: z.string().optional()
          .describe("Filter by chain ID"),
        format: z.nativeEnum(ResponseFormat).optional().default(ResponseFormat.MARKDOWN)
          .describe("Response format: 'json' for raw data or 'markdown' for formatted text")
      },
      READ_ONLY,
      async ({ receiver, chainId, format }) => {
        try {
          const summary = await getPartnerSummary(receiver, chainId);
          if (!summary) {
            return {
              content: [{ type: "text", text: `Partner not found: ${receiver}` }]
            };
          }
          return {
            content: [{
              type: "text",
              text: `## Partner Summary\n\n` + formatResponse(summary, format)
            }]
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error: ${error instanceof Error ? error.message : "Unknown error"}` }],
            isError: true
          };
        }
      }
    );
  • API drift check contract for sodax_get_partner_summary: maps to GET /partners/:receiver/summary with params [receiver, chainId], required [receiver], and expected response fields.
    "GET /partners/:receiver/summary": {
      tool: "sodax_get_partner_summary",
      params: ["receiver", "chainId"],
      requiredParams: ["receiver"],
      responseFields: ["receiver", "chainId", "feeByInputToken", "volumeByOutputToken"],
  • src/index.ts:44-48 (registration)
    Tool registration is triggered by registerSodaxApiTools(server) in the main server setup.
      registerSodaxApiTools(server);
      await registerGitBookProxyTools(server);
    
      return server;
    }
  • Analytics tool group mapping: sodax_get_partner_summary is categorized as 'api' for PostHog tracking.
    sodax_get_partner_summary: "api",
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description adds the specific behavior of returning a summary. However, it does not elaborate on what the summary includes (e.g., volume amounts, activity counts) or any other behavioral constraints.

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 sentence of 12 words, conveying the core purpose without any extraneous information. Every word earns its place.

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 tool has 3 parameters, all described in schema, and no output schema, the description is adequate but could be more complete by detailing what the summary contains (e.g., volume metrics, activity types). The annotations cover safety, so additional behavioral context is not critical.

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%, and the description does not add meaningful new information beyond what the schema already provides for each parameter (e.g., 'receiver', 'chainId', 'format'). It repeats the purpose but does not clarify the relationship between parameters.

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 (get), the resource (volume and activity summary for an integration partner), and the identifier (receiver address). It distinguishes itself from the sibling tool sodax_get_partners, which lists all partners, by focusing on a specific partner.

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 does not provide guidance on when to use this tool versus alternatives (e.g., sodax_get_partners, sodax_get_volume). An agent is not told when not to use it or what prerequisites exist beyond the required receiver parameter.

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