Skip to main content
Glama

ArcanumFleet 10-Node Consensus Vote

arcanum_consensus_vote
Read-onlyIdempotent

Use this when you want a final BUY or SKIP trade decision with confidence score from the 10-node Consensus Admiral for a specific Solana mint. Costs 0.01 USDC via x402.

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": {
      "mint": "<mint>"
    },
    "name": "arcanum_consensus_vote"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesBase58 Solana SPL token mint address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / mint / description
      Previous value: -"Solana token mint address"New value: +"Base58 Solana SPL token mint address"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, and idempotent behavior, so the bar is lower. The description adds meaningful context beyond that: a payment requirement of 0.01 USDC via x402 and that the result includes a BUY or SKIP verdict plus confidence score.

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?

It is a single front-loaded sentence with the use condition first, the output second, and the cost third. Every clause carries useful information and there is no wasted wording.

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 full schema coverage and no output schema, the description covers the essential outcome and the payment model. It stops short of describing latency, failure modes, or what confidence scores mean, but it is substantially complete.

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 coverage is 100%, so the mint parameter is already fully documented as a Base58 Solana SPL token mint address. The description only restates that a specific Solana mint is required and adds no new syntax, format, or validation detail.

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 states a specific verb-plus-resource: get a final BUY or SKIP trade decision with a confidence score from the 10-node Consensus Admiral for a Solana mint. It is easy to distinguish from analytical siblings in spirit, though it does not name a sibling to route against explicitly.

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?

It gives a clear when-to-use condition: when the agent wants a final BUY or SKIP decision for a specific mint. It does not state when not to use it or which sibling to prefer for supporting analysis, but the context is clear.

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