Skip to main content
Glama
buildwithgrove

Grove's MCP Server for Pocket Network

get_solana_prioritization_fees

Retrieve recent Solana transaction prioritization fees to optimize network costs. Query fees for specific accounts or networks using Grove's MCP Server.

Instructions

Get recent prioritization fees for Solana transactions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressesNoOptional: Account addresses to get fees for
networkNoNetwork type (defaults to mainnet)

Implementation Reference

  • Handler logic in handleSolanaTool switch statement that extracts arguments, calls SolanaService.getRecentPrioritizationFees, and formats the response.
    case 'get_solana_prioritization_fees': {
      const addresses = args?.addresses as string[] | undefined;
      const network = (args?.network as 'mainnet' | 'testnet') || 'mainnet';
    
      const result = await solanaService.getRecentPrioritizationFees(addresses, network);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
        isError: !result.success,
      };
    }
  • Core service method that invokes the Solana RPC 'getRecentPrioritizationFees' via the blockchain RPC service, handling optional addresses parameter.
    async getRecentPrioritizationFees(
      addresses?: string[],
      network: 'mainnet' | 'testnet' = 'mainnet'
    ): Promise<EndpointResponse> {
      const service = this.blockchainService.getServiceByBlockchain('solana', network);
    
      if (!service) {
        return {
          success: false,
          error: `Solana service not found for ${network}`,
        };
      }
    
      const params = addresses ? [addresses] : [];
    
      return this.blockchainService.callRPCMethod(
        service.id,
        'getRecentPrioritizationFees',
        params
      );
    }
  • Tool registration in registerSolanaHandlers function, defining name, description, and input schema.
    {
      name: 'get_solana_prioritization_fees',
      description: 'Get recent prioritization fees for Solana transactions',
      inputSchema: {
        type: 'object',
        properties: {
          addresses: {
            type: 'array',
            items: { type: 'string' },
            description: 'Optional: Account addresses to get fees for',
          },
          network: {
            type: 'string',
            enum: ['mainnet', 'testnet'],
            description: 'Network type (defaults to mainnet)',
          },
        },
      },
    },
  • Input schema definition for the tool, specifying optional addresses array and network enum.
    inputSchema: {
      type: 'object',
      properties: {
        addresses: {
          type: 'array',
          items: { type: 'string' },
          description: 'Optional: Account addresses to get fees for',
        },
        network: {
          type: 'string',
          enum: ['mainnet', 'testnet'],
          description: 'Network type (defaults to mainnet)',
        },
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does without behavioral details. It doesn't disclose whether this is a read-only operation, what 'recent' means (timeframe), potential rate limits, authentication needs, or what the output format looks like. This is inadequate for a tool with no annotation coverage.

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 directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 no annotations and no output schema, the description is incomplete for a tool that retrieves financial data. It doesn't explain what 'prioritization fees' are, how they're calculated, what time range 'recent' covers, or what the return structure looks like. For a tool with no structured output documentation, this leaves significant 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 description coverage is 100%, so the schema already fully documents both parameters ('addresses' and 'network'). The description adds no additional parameter semantics beyond what's in the schema, such as clarifying 'recent' timeframe or fee calculation details. Baseline 3 is appropriate when schema does all the work.

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

Purpose4/5

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

The description clearly states the action ('Get') and resource ('recent prioritization fees for Solana transactions'), making the purpose immediately understandable. It doesn't distinguish from siblings like 'get_solana_fee_for_message' or 'get_solana_transaction', but it's specific enough to understand what data is being retrieved.

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 'get_solana_fee_for_message' or 'get_solana_transaction', nor does it mention prerequisites or context for usage. It's a standalone statement without comparative or contextual information.

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/buildwithgrove/mcp-pocket'

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