Skip to main content
Glama
Sign In
solana-agent-mcp

solana-agent-mcp

by KorroAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

solana_request_airdrop

Request a SOL airdrop on Solana devnet or testnet to fund development or testing. Not available on mainnet.

Instructions

Request SOL airdrop on devnet (testnet only, not mainnet)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "solana_request_airdrop"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The description only says 'Request SOL airdrop', without detailing side effects, return value, idempotency, authorization requirements, or whether the airdrop goes to the current user. This lack of detail is insufficient for an agent to understand the tool's 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 sentence that efficiently conveys the core purpose and a key constraint. No unnecessary words or repetition.

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 the simplicity of the tool (no parameters, no output schema, no annotations), the description is incomplete. It fails to specify important details such as the recipient of the airdrop, the amount, or whether a wallet connection is required. An agent would need more context to use the tool correctly.

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?

The input schema has no parameters, and the schema description coverage is 100%. Thus the baseline score of 3 applies, and the description does not need to add parameter semantics because there are none.

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 'Request', the resource 'SOL airdrop', and the specific environment 'devnet (testnet only, not mainnet)'. It effectively distinguishes this tool from sibling tools like solana_get_balance or solana_get_price, which have 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 Guidelines4/5

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

The description explicitly states that the tool should be used only on devnet/testnet and not on mainnet, providing clear contextual use guidance. However, it does not mention any alternative tools or scenarios where this tool should not be used beyond the network restriction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools