Get latest blockhash for transaction building. Returns blockhash + lastValidBlockHeight.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| value | Yes | ||
| context | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description only states the return fields but fails to disclose behavioral traits such as idempotency, side effects, or rate limits. A read operation is implied but not confirmed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise with two front-loaded sentences, no wasted words, and directly conveys the tool's purpose and return value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (zero parameters, clear return fields), the description is complete. The output schema is stated in the description, so no further detail is necessary.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so the description adds no parameter-level information beyond the schema. Baseline score of 4 applies as per guidelines for zero-parameter tools.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get', resource 'latest blockhash', and purpose 'for transaction building', making it distinct from sibling tools like solana_getSlot or solana_getBalance.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context that this tool is used for transaction building, implying it should be called before building a transaction. However, it lacks explicit when-not or alternative tool references.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tool pairs overlap in function: aex402_quote vs aex402_buildSwap, search vs search_tokens vs discover_programs, describe_program vs reconstruct_abi, and mcp_linq vs agent_delegate. Descriptions attempt to differentiate, but boundaries are fuzzy and an agent could easily select the wrong one when uncertain.
Naming is inconsistent: some tools use camelCase (aex402_buildSwap) while most use snake_case, verbs vary widely (build, get, list, quote, search, describe, discover, launch, delegate, chat), and there is no uniform verb_noun pattern. This makes predicting tool names difficult.
32 tools is excessive for a single MCP server, exceeding the 25+ threshold. While the scope is broad (AMM, bridge, AI, RPC, discovery, launchpad), many tools could be consolidated (e.g., search tools) or are too fine-grained (multiple solana_get* tools).
Core workflows are well covered: AMM (quote/build/get/list), bridge (quote/status), AI (chat/delegate/linq), Solana and EVM RPCs, search/discovery plus health check, launchpad, and payment help. Minor gaps include no direct bridge history or AMM execution, but these are intentional in a non-custodial design.
