Skip to main content
Glama
monostate

Crossmint HR Airdrop MCP

by monostate

get_state

Retrieve the current status of Solana token airdrops to employees, enabling HR teams to monitor progress and ensure efficient role-based distribution.

Instructions

Get the current state of the airdrop process

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the get_state tool, returning formatted text of the current airdrop process state including wallet connection, token creation, employee count, airdrop status, and email status.
      private async handleGetState() {
        return {
          content: [
            {
              type: 'text',
              text: `
    Current Airdrop State:
    - Connected Wallet: ${this.state.connectedWallet ? 'Yes' : 'No'}${
                this.state.connectedWallet
                  ? `\n  Public Key: ${this.state.connectedWallet.publicKey}\n  SOL Balance: ${this.state.connectedWallet.solBalance} SOL`
                  : ''
              }
    - Created Token: ${this.state.createdToken ? 'Yes' : 'No'}${
                this.state.createdToken
                  ? `\n  Name: ${this.state.createdToken.name}\n  Symbol: ${this.state.createdToken.symbol}\n  Supply: ${this.state.createdToken.supply.toLocaleString()}\n  Mint Address: ${this.state.createdToken.mintAddress}`
                  : ''
              }
    - Employees: ${this.state.employees.length}
    - Airdrop Status: ${this.state.airdropStatus.completed ? 'Completed' : this.state.airdropStatus.started ? 'In Progress' : 'Not Started'}
    - Emails Status: ${this.state.emailsStatus.sent ? 'Sent' : 'Not Sent'}
              `.trim(),
            },
          ],
        };
      }
  • src/server.ts:298-304 (registration)
    Registration of the 'get_state' tool in the MCP server tools list, including name, description, and empty input schema (no parameters required).
      name: 'get_state',
      description: 'Get the current state of the airdrop process',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/server.ts:336-337 (registration)
    Dispatch logic in the tool request handler switch statement that routes 'get_state' calls to the handleGetState method.
    case 'get_state':
      return await this.handleGetState();
  • Input schema definition for the 'get_state' tool, specifying an empty object (no input parameters).
    inputSchema: {
      type: 'object',
      properties: {},
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a 'Get' operation, implying it's likely read-only, but doesn't specify if it requires authentication, has rate limits, or what the state includes (e.g., progress, errors). This leaves significant gaps for a tool with potential complexity.

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 directly states the tool's purpose without any fluff or redundancy. It's front-loaded and efficiently communicates the essential information, making it highly concise and well-structured.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the 'state' includes (e.g., status, progress, errors) or behavioral aspects like authentication needs. For a tool that might return complex state information, this leaves the agent with insufficient context.

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 there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately avoids unnecessary details, earning a high score for this context.

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 ('current state of the airdrop process'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'start_airdrop' or 'check_balance', which might also relate to airdrop status, so it doesn't reach the highest score.

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. It doesn't mention prerequisites, such as whether an airdrop must be started first, or contrast with other tools like 'check_balance' for wallet status, leaving usage context unclear.

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/monostate/Employees-Airdrop-Rewards-MCP'

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