Skip to main content
Glama

arcium_sealed_bid

Encrypt and submit a sealed bid to an onchain Solana auction. The bid stays hidden until the auction closes.

Instructions

Submit an encrypted sealed bid to an onchain auction. Bid stays hidden until close.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bid_amountYesBid amount in lamports (string for precision)
auction_addressYesSolana address of the auction program
Behavior4/5

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

The description discloses that the bid is encrypted and stays hidden until auction close, which is key behavioral information. However, it does not mention other potential behaviors like bid modification or cancellation.

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 that is front-loaded with the action and resource, containing no wasted words.

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?

For a simple submission tool with no output schema, the description covers the essential purpose but lacks details on return values or post-submission behavior, leaving some gaps.

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 coverage is 100%, so baseline is 3. The description does not add extra meaning beyond the schema; it only restates the context of encrypted sealed bids.

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 verb 'Submit' and the specific resource 'encrypted sealed bid to an onchain auction', distinguishing it from sibling tools like arcium_private_vote.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for onchain auctions with sealed bids but provides no explicit guidance on when to use this tool versus alternatives or when not to use it.

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/babakarto/arcium-mcp'

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