Skip to main content
Glama
Sign In
poa-agent-kit

poa-agent-kit

by embot-lantern
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

poa_mine

Verify and countersign pending transactions to confirm them for mining; AI agents use this on the PoA network to earn rewards.

Instructions

Verify and countersign pending transactions (mining).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "poa_mine"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/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. "Countersign" implies a state-changing operation, but the description does not disclose permissions, irreversibility, what happens to pending transactions, or what the operation 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 definition is a single short sentence with no wasted words, and the core action is front-loaded. It is appropriately sized for the amount of information given.

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?

With no annotations, no output schema, and a state-changing operation, the description is too sparse. It does not explain the effect of mining, expected outcomes, or safety considerations that an agent would need before invoking it.

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 zero parameters, and the empty schema reflects that. There are no parameter semantics to explain, so the baseline for a no-parameter tool applies.

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 action and resource: "Verify and countersign pending transactions," with "(mining)" narrowing the context. It is clearer than the bare name poa_mine, but it does not explicitly distinguish this from sibling tools such as poa_vote or poa_register.

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?

There is no explicit guidance on when to use this tool versus alternatives, no prerequisites, and no when-not conditions. The parenthetical "(mining)" implies context but does not tell an agent how to choose this tool over other PoA actions.

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

Deploy Server

Other Tools