Skip to main content
Glama
joadataarg

MIST.cash MCP Server

by joadataarg

obtener_configuracion_chamber

Retrieve Chamber contract configuration details such as address, network, and supported tokens for the MIST.cash privacy-preserving payment protocol on Starknet.

Instructions

Get Chamber contract configuration including contract address, network, and supported tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkNoStarknet networkmainnet

Implementation Reference

  • The handler function for 'obtener_configuracion_chamber' tool. Validates input params using schema, determines contract address based on network (mainnet/sepolia), assembles config with supported tokens, and returns structured response.
    export async function obtenerConfiguracionChamber(params) {
        // Validate parameters
        const validated = ObtenerConfiguracionChamberSchema.parse(params);
        try {
            const contractAddress = validated.network === 'mainnet'
                ? CHAMBER_ADDR_MAINNET
                : CHAMBER_ADDR_SEPOLIA;
            const config = {
                contract_address: contractAddress,
                network: validated.network,
                supported_tokens: SUPPORTED_TOKENS[validated.network]
            };
            return {
                success: true,
                config,
                token_info: {
                    ETH: 'Native Starknet token',
                    USDC: 'USD Coin stablecoin',
                    USDT: 'Tether stablecoin',
                    DAI: 'DAI stablecoin'
                }
            };
        }
        catch (error) {
            throw new Error(`Failed to get Chamber configuration: ${error.message}`);
        }
    }
  • Zod schema for input validation of the tool. Defines optional 'network' parameter with enum ['mainnet', 'sepolia'] defaulting to 'mainnet'.
    export const ObtenerConfiguracionChamberSchema = z.object({
        network: NetworkSchema
    });
  • src/index.ts:141-155 (registration)
    Tool registration in ListToolsRequestSchema handler. Provides the tool name, description, and input schema for MCP discovery.
    {
        name: 'obtener_configuracion_chamber',
        description: 'Get Chamber contract configuration including contract address, network, and supported tokens.',
        inputSchema: {
            type: 'object',
            properties: {
                network: {
                    type: 'string',
                    enum: ['mainnet', 'sepolia'],
                    description: 'Starknet network',
                    default: 'mainnet',
                },
            },
        },
    },
  • src/index.ts:206-214 (registration)
    Dispatch logic in CallToolRequestSchema handler. Routes calls to this tool name to the handler function and formats response.
    case 'obtener_configuracion_chamber':
        return {
            content: [
                {
                    type: 'text',
                    text: JSON.stringify(await obtenerConfiguracionChamber(args || {}), null, 2),
                },
            ],
        };
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'), but doesn't cover aspects like authentication needs, rate limits, error conditions, or what happens if the configuration isn't found. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 purpose and specifies the retrieved data. There is no wasted language or redundancy, making it appropriately sized for the tool's complexity.

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 one parameter with full schema coverage and no output schema, the description is adequate but incomplete. It explains what configuration is retrieved but doesn't cover behavioral aspects like error handling or response format. For a read-only tool with minimal parameters, it meets basic needs but lacks depth for robust agent use.

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 the schema already documents the single parameter ('network') with its type, enum values, and default. The description mentions 'network' as part of the retrieved configuration but doesn't add syntax, format, or usage details beyond what the schema provides. 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 ('Get') and the resource ('Chamber contract configuration'), specifying what information is retrieved (contract address, network, and supported tokens). It distinguishes from siblings by focusing on configuration retrieval rather than transaction-related operations, though it doesn't explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context for retrieving configuration, or differentiate from potential sibling tools that might handle similar data. Usage is implied only by the tool's name and description.

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/joadataarg/Mcp-mistcash'

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