Skip to main content
Glama

ADD_COLLATERAL

Increase collateral in your Borrow Automated Market Maker (BAMM) position by specifying the BAMM contract address, collateral token, and amount on the Fraxtal blockchain.

Instructions

Add collateral to your BAMM position

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesThe amount of collateral to add
bammAddressYesThe address of the BAMM contract
collateralTokenNoThe address of the collateral token
collateralTokenSymbolNoThe symbol of the collateral token (e.g., 'IQT')

Implementation Reference

  • The execute function of the ADD_COLLATERAL tool, which validates inputs, initializes services, calls the AddCollateralService, and returns formatted success or error messages.
    execute: async (params) => {
    	try {
    		if (!params.collateralToken && !params.collateralTokenSymbol) {
    			return "Error: Either collateralToken address or collateralTokenSymbol is required";
    		}
    
    		const privateKey = process.env.WALLET_PRIVATE_KEY;
    		if (!privateKey) {
    			return "Error: WALLET_PRIVATE_KEY environment variable is not set. Please set it with your wallet's private key (without 0x prefix).";
    		}
    
    		const walletService = new WalletService(privateKey);
    		const addCollateralService = new AddCollateralService(walletService);
    
    		const result = await addCollateralService.execute({
    			bammAddress: params.bammAddress as Address,
    			collateralToken: params.collateralToken as Address | undefined,
    			collateralTokenSymbol: params.collateralTokenSymbol,
    			amount: params.amount,
    		});
    
    		return dedent`
           ✅ Collateral Addition Successful
    
           🌐 BAMM Address: ${params.bammAddress}
           🔒 Amount: ${formatNumber(Number(params.amount))}
           💰 Token: ${params.collateralTokenSymbol ?? params.collateralToken}
           🔗 Transaction: ${result.txHash}
    
           Collateral has been added to your BAMM position.
         `;
    	} catch (error) {
    		if (error instanceof Error) {
    			return dedent`
             ❌ Collateral Addition Failed
    
             Error: ${error.message}
    
             Please verify your inputs and try again.
           `;
    		}
    		return "An unknown error occurred while adding collateral";
    	}
    },
  • Zod schema defining the input parameters for the ADD_COLLATERAL tool: bammAddress, amount, optional collateralToken or collateralTokenSymbol.
    const addCollateralToolParams = z.object({
    	bammAddress: z
    		.string()
    		.regex(/^0x[a-fA-F0-9]{40}$/)
    		.describe("The address of the BAMM contract"),
    	amount: z.string().min(1).describe("The amount of collateral to add"),
    	collateralToken: z
    		.string()
    		.regex(/^0x[a-fA-F0-9]{40}$/)
    		.optional()
    		.describe("The address of the collateral token"),
    	collateralTokenSymbol: z
    		.string()
    		.optional()
    		.describe("The symbol of the collateral token (e.g., 'IQT')"),
    });
  • src/index.ts:19-19 (registration)
    Registration of the addCollateralTool in the FastMCP server instance.
    server.addTool(addCollateralTool);
  • AddCollateralService class that handles the core logic: resolves token, validates, checks balance/approval, and executes the BAMM contract's executeActions for adding collateral.
    export class AddCollateralService {
    	constructor(private walletService: WalletService) {}
    
    	async execute(params: AddCollateralParams): Promise<{ txHash: string }> {
    		let { bammAddress, collateralToken, collateralTokenSymbol, amount } =
    			params;
    		if (!collateralToken && !collateralTokenSymbol) {
    			throw new Error(
    				"Either collateralToken or collateralTokenSymbol is required",
    			);
    		}
    		const publicClient = this.walletService.getPublicClient();
    		const walletClient = this.walletService.getWalletClient();
    
    		if (!walletClient || !walletClient.account) {
    			throw new Error("Wallet client is not initialized");
    		}
    
    		const userAddress = walletClient.account.address;
    		const amountInWei = BigInt(Number(amount) * 1e18);
    		try {
    			if (collateralTokenSymbol) {
    				collateralToken = await getTokenAddressFromSymbol(
    					collateralTokenSymbol,
    				);
    			}
    
    			if (!collateralToken) {
    				throw new Error("Could not resolve collateral token address");
    			}
    
    			const tokenValidation = await validateTokenAgainstBAMM(
    				bammAddress,
    				collateralToken,
    				publicClient,
    			);
    
    			await checkTokenBalance(
    				collateralToken,
    				userAddress,
    				amountInWei,
    				publicClient,
    			);
    			await ensureTokenApproval(
    				collateralToken,
    				bammAddress,
    				amountInWei,
    				publicClient,
    				walletClient,
    			);
    
    			const currentTime = Math.floor(Date.now() / 1000);
    			const deadline = BigInt(currentTime + 300);
    
    			const action = {
    				token0Amount: tokenValidation.isToken0 ? amountInWei : 0n,
    				token1Amount: tokenValidation.isToken1 ? amountInWei : 0n,
    				rent: 0n,
    				to: userAddress,
    				token0AmountMin: 0n,
    				token1AmountMin: 0n,
    				closePosition: false,
    				approveMax: false,
    				v: 0,
    				r: "0x0000000000000000000000000000000000000000000000000000000000000000" as `0x${string}`,
    				s: "0x0000000000000000000000000000000000000000000000000000000000000000" as `0x${string}`,
    				deadline,
    			};
    			const { request: executeRequest } = await publicClient.simulateContract({
    				address: bammAddress,
    				abi: BAMM_ABI,
    				functionName: "executeActions",
    				args: [action],
    				account: walletClient.account,
    			});
    			const txHash = await walletClient.writeContract(executeRequest);
    			await publicClient.waitForTransactionReceipt({ hash: txHash });
    			return { txHash };
    		} catch (error) {
    			console.error("Error in add collateral service:", error);
    			throw Error("Error in add collateral service");
    		}
    	}
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It implies a write operation ('Add') but doesn't specify whether this requires authentication, what permissions are needed, potential transaction costs, rate limits, or what happens on success/failure. For a financial tool with no annotation coverage, this is a significant gap in transparency.

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 gets straight to the point with zero wasted words. It's appropriately sized for a tool with good schema documentation and follows the principle of front-loading the core purpose.

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?

For a financial transaction tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after adding collateral, potential side effects, error conditions, or return values. Given the complexity of DeFi operations and lack of structured behavioral information, the description should provide more context about the operation's consequences.

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 all four parameters thoroughly. The description adds no additional parameter information beyond what's in the schema, not explaining relationships between parameters (e.g., how collateralToken and collateralTokenSymbol relate) or providing usage examples. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Add collateral to your BAMM position' clearly states the action (add) and target (collateral to BAMM position), but it's somewhat vague about what 'BAMM position' means in this context. It distinguishes from siblings like REMOVE_COLLATERAL but doesn't fully clarify the financial/DeFi context compared to tools like BORROW or LEND.

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 REMOVE_COLLATERAL or other sibling tools. It doesn't mention prerequisites, timing considerations, or typical scenarios for adding collateral in a DeFi context, leaving the agent to infer usage from the tool name alone.

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/IQAIcom/mcp-bamm'

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