Skip to main content
Glama

get_external_market_config

Retrieve current configuration for external market data API to facilitate accurate querying and integration with EDUCHAIN and SailFish DEX operations.

Instructions

Get the current configuration for external market data API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 'get_external_market_config' tool. It calls external_market.getConfig() and returns the configuration as JSON or an error message.
    case 'get_external_market_config': {
      try {
        const config = external_market.getConfig();
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(config, null, 2),
            },
          ],
        };
      } catch (error) {
        console.error('Error getting external market config:', error);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({ 
                error: 'Failed to get external market API configuration',
                message: (error as Error).message
              }, null, 2),
            },
          ],
          isError: true,
        };
      }
  • src/index.ts:667-674 (registration)
    Registration of the 'get_external_market_config' tool in the ListToolsRequestSchema handler, including its name, description, and input schema (empty object).
      name: 'get_external_market_config',
      description: 'Get the current configuration for external market data API',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • Helper function getConfig() exported from external_market.ts that returns a copy of the current external market configuration. This is called by the tool handler.
    /**
     * Get the current external market API configuration
     */
    export function getConfig(): typeof config {
      return { ...config };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a read operation ('Get'), implying it's likely non-destructive, but doesn't specify if it requires authentication, has rate limits, or what the return format looks like. This leaves significant gaps for a tool interacting with an external API.

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, clear sentence with zero waste—it directly states the tool's purpose without fluff or redundancy. It's appropriately sized for a no-parameter tool and front-loaded with essential information.

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

Completeness2/5

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

Given the complexity of interacting with an external market data API, the description is incomplete. With no annotations and no output schema, it fails to explain what the configuration includes (e.g., endpoints, keys, limits) or the response structure. This makes it inadequate for an agent to use the tool effectively without additional 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 tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The description appropriately doesn't mention parameters, earning a baseline score of 4 for not adding unnecessary information.

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 clearly states the verb ('Get') and resource ('current configuration for external market data API'), making the purpose understandable. However, it doesn't explicitly distinguish this tool from its sibling 'update_external_market_config' beyond the verb difference, nor does it clarify what 'configuration' entails compared to 'data' from 'get_external_market_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 provides no guidance on when to use this tool versus alternatives like 'update_external_market_config' or 'get_external_market_data'. It lacks context about prerequisites, such as whether the API must be set up first, or any exclusions for usage.

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

Related 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/SailFish-Finance/educhain-ai-agent-kit'

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