Skip to main content
Glama
CoinStatsHQ

CoinStats MCP Server

Official

add-portfolio-transaction

Add cryptocurrency transactions to a manual portfolio in CoinStats, specifying coin, type, date, amount, and price for accurate tracking.

Instructions

Add a transaction to a manual portfolio.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shareTokenNoPortfolio share token
coinIdYesCoin ID
typeYesTransaction type
dateYesTransaction date in ISO format
amountYesTransaction amount
priceYesPrice per coin
feeNoTransaction fee
notesNoTransaction notes

Implementation Reference

  • Tool configuration including name, description, endpoint, HTTP method, and Zod input schema for parameters.
    {
        name: 'add-portfolio-transaction',
        description: 'Add a transaction to a manual portfolio.',
        endpoint: '/portfolio/transaction',
        method: 'POST',
        parameters: {
            shareToken: z.string().optional().describe('Portfolio share token'),
            // This endpoint requires a request body which would need to match the AddTransactionDto schema
            // For simplicity, we're defining a basic structure that matches the expected input
            coinId: z.string().describe('Coin ID'),
            type: z.string().describe('Transaction type'),
            date: z.string().describe('Transaction date in ISO format'),
            amount: z.number().describe('Transaction amount'),
            price: z.number().describe('Price per coin'),
            fee: z.number().optional().describe('Transaction fee'),
            notes: z.string().optional().describe('Transaction notes'),
        },
    },
  • src/index.ts:17-18 (registration)
    Registers the add-portfolio-transaction tool (included in allToolConfigs) with the MCP server by calling registerTools.
    // Register all tools from configurations
    registerTools(server, allToolConfigs);
  • Generic handler for the tool: determines if local or API, for API calls universalApiHandler with appropriate params/body based on method (for POST uses params as body).
    toolConfigs.forEach((config) => {
        server.tool(config.name, config.description, config.parameters, async (params: Record<string, any>) => {
            // Handle local operations
            if (config.isLocal) {
                // Handle specific local tools
                if (config.name === 'save-share-token') {
                    await saveToCache('shareToken', params.shareToken);
                    return {
                        content: [
                            {
                                type: 'text',
                                text: 'Share token saved successfully',
                            },
                        ],
                    };
                }
    
                if (config.name === 'get-share-token') {
                    const shareToken = await getFromCache('shareToken');
    
                    return {
                        content: [
                            {
                                type: 'text',
                                text: shareToken ? shareToken : 'No share token found in cache',
                                isError: !shareToken,
                            },
                        ],
                    };
                }
                // Future local tools can be added here
    
                // Default response for unhandled local tools
                return {
                    content: [
                        {
                            type: 'text',
                            text: 'Operation completed',
                        },
                    ],
                };
            }
    
            // Handle API operations
            const basePath = config.basePath || COINSTATS_API_BASE;
            const method = config.method || 'GET';
    
            // Methods that typically have a request body
            const bodyMethods = ['POST', 'PUT', 'PATCH', 'DELETE'];
    
            // For GET/DELETE requests, all params go in the URL
            // For POST/PUT/PATCH, send params as the body
            if (bodyMethods.includes(method.toUpperCase())) {
                return universalApiHandler(basePath, config.endpoint, method, {}, params);
            } else {
                return universalApiHandler(basePath, config.endpoint, method, params);
            }
        });
  • Core HTTP request handler: processes path/query params, makes fetch to CoinStats API with API key, handles errors, returns MCP-formatted response (JSON string).
    export async function universalApiHandler<T>(
        basePath: string,
        endpoint: string,
        method: string = 'GET',
        params: Record<string, any> = {},
        body?: any
    ): Promise<{
        content: Array<{ type: 'text'; text: string; isError?: boolean }>;
    }> {
        try {
            // Handle path parameters - replace {paramName} in endpoint with actual values
            let processedEndpoint = endpoint;
            let processedParams = { ...params };
    
            // Find all path parameters in the endpoint (e.g., {coinId}, {id}, {type})
            const pathParamMatches = endpoint.match(/\{([^}]+)\}/g);
    
            if (pathParamMatches) {
                for (const match of pathParamMatches) {
                    const paramName = match.slice(1, -1); // Remove { and }
    
                    if (processedParams[paramName] !== undefined) {
                        // Replace the placeholder with the actual value
                        processedEndpoint = processedEndpoint.replace(match, processedParams[paramName]);
                        // Remove the parameter from query params since it's now part of the path
                        delete processedParams[paramName];
                    } else {
                        throw new Error(`Required path parameter '${paramName}' is missing`);
                    }
                }
            }
    
            // MCP clients might not support '~' in parameter names, so we replace '-' with '~' specifically for the /coins endpoint before making the request.
            if (endpoint === '/coins') {
                processedParams = Object.entries(processedParams).reduce((acc, [key, value]) => {
                    acc[key.replace(/-/g, '~')] = value;
                    return acc;
                }, {} as Record<string, any>);
            }
    
            const url = `${basePath}${processedEndpoint}`;
            const data = await makeRequestCsApi<T>(url, method, processedParams, body);
    
            if (!data) {
                return {
                    content: [{ type: 'text', text: 'Something went wrong', isError: true }],
                };
            }
    
            return {
                content: [
                    {
                        type: 'text',
                        text: JSON.stringify(data),
                    },
                ],
            };
        } catch (error) {
            return {
                content: [{ type: 'text', text: `Error: ${error}`, isError: true }],
            };
        }
    }
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. 'Add a transaction' implies a write/mutation operation, but the description doesn't address critical aspects like required permissions, whether the operation is idempotent, error handling, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap.

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 directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 that this is a mutation tool with no annotations, no output schema, and 8 parameters (5 required), the description is incomplete. It doesn't cover behavioral aspects like side effects, error conditions, or return values, which are critical for an agent to use the tool correctly in a financial context.

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%, meaning all parameters are documented in the input schema. The description doesn't add any meaning beyond what the schema provides (e.g., it doesn't explain what 'manual portfolio' means or provide examples for 'type' values). With high schema coverage, the baseline score of 3 is appropriate.

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 action ('Add a transaction') and the target resource ('to a manual portfolio'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from sibling tools like 'get-portfolio-transactions' or 'transactions-sync', which are related but serve different purposes.

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. It doesn't mention prerequisites (e.g., needing a portfolio share token), exclusions, or how it differs from sibling tools like 'transactions-sync' or 'get-portfolio-transactions', leaving the agent without context for tool selection.

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/CoinStatsHQ/coinstats-mcp'

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