Skip to main content
Glama
tywenk

Model Context Protocol Server for Solana Client

by tywenk

get_identity

Retrieve the identity public key of the current node interacting with the Solana blockchain using the MCP server. Simplifies node identification for users managing blockchain operations.

Instructions

Returns the identity pubkey for the current node.

Returns: str: Node identity in the format "Node identity: {identity}"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_identity' MCP tool. It uses the Solana AsyncClient to fetch the current node's identity pubkey and formats it as a string response.
    @mcp.tool()
    async def get_identity() -> str:
        """Returns the identity pubkey for the current node.
    
        Returns:
            str: Node identity in the format "Node identity: {identity}"
        """
        async with AsyncClient(rpc_url) as client:
            identity = await client.get_identity()
            return f"Node identity: {identity}"
  • src/server.py:153-153 (registration)
    The @mcp.tool() decorator registers the get_identity function as an MCP tool.
    @mcp.tool()
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a string in a specific format, which is useful behavioral context. However, it lacks details on potential errors, latency, or side effects (e.g., if this is a read-only operation, though implied by 'Returns').

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 front-loaded with the core purpose in the first sentence, followed by return format details. Both sentences are essential, with zero waste, making it highly concise and well-structured for a simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is complete enough by stating what it returns and the format. It could improve by mentioning if it's read-only or has any constraints, but for a basic identity fetch, it covers the essentials adequately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description does not add parameter semantics beyond the schema, but with no parameters, a baseline of 4 is appropriate as there is no gap to compensate for.

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 tool's purpose with a specific verb ('Returns') and resource ('identity pubkey for the current node'), and it distinguishes from siblings by focusing on node identity rather than account, block, or transaction data. The description explicitly mentions the return format, which adds clarity.

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 when the node's identity is needed, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., other 'get_' tools for different data). No exclusions or prerequisites are mentioned, leaving usage context somewhat vague.

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/tywenk/mcp-sol'

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