Skip to main content
Glama

aui_verify_solana_key

Verify a 0.1 SOL transfer to Gn4B5GnuR5dWhP9dGWJgsaWDNnhkSBTjDyrPSyrevM23 on Solana mainnet and return a 500-execution Hosted Production AUI key (includes hosted Gemini inference + SMS/Email sharing).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "signature": "<signature>"
    },
    "name": "aui_verify_solana_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
signatureYesSolana mainnet transaction signature.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the whole behavioral burden, and it does disclose the amount, destination, network, and the shape of the issued credential. It says nothing about failure modes (insufficient/late/unconfirmed transfer), replay of the same signature, idempotency, or whether the key is single-use, which matters for an operation that mints a credential.

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?

A single front-loaded sentence carrying the action, the constraint, and the payoff in one pass, with no redundant framing or filler.

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?

For a one-parameter tool with no output schema and no annotations, the description covers the action and the returned artifact adequately. The remaining gap is behavioral edge cases, which the missing annotations would otherwise have supplied.

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?

One required parameter with 100% schema coverage ('Solana mainnet transaction signature'), so the baseline is 4. The description does not add syntax or format detail beyond the schema, but nothing is left ambiguous.

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?

Names a specific verb (verify), a specific resource (a 0.1 SOL mainnet transfer to a stated address), and the concrete artifact it returns (a 500-execution Hosted Production AUI key including Gemini inference and sharing). Nothing here overlaps with the sibling tools, which claim trials, generate UI, or share widgets.

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 makes clear the precondition implicitly — a SOL transfer already made to the named address — but never states when to pick this route over aui_claim_free_trial to obtain a key, nor what to do if the transfer is absent. Usage is inferable rather than instructed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources