Skip to main content
Glama

mine

Earn SHELL tokens by submitting an agent UUID; requires trust score ≥1, pays by trust level and zone, and allows one claim per day.

Instructions

Mine SHELL tokens. Requires trust score >= 1. Amount depends on trust level and zone. Cooldown: 1 per day.

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": {
      "uuid": "<uuid>"
    },
    "name": "mine"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesAgent UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full disclosure burden and does well: it states a precondition (trust score >= 1), a rate limit (1 per day), and that the reward is non-deterministic ('Amount depends on trust level and zone'). It omits what happens on rejection and does not explicitly label the operation as state-changing, though 'mine' implies earning/mutation.

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?

Four short sentences, purpose first, then constraints, outcome variability, and rate limit in descending order of importance. No filler or restatement of the tool name.

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 purpose, eligibility, frequency limit, and the variable reward. The remaining gap is failure behavior and what the caller receives back, which is minor given the tool's simplicity.

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?

The single parameter has 100% schema description coverage ('Agent UUID'), so the schema already carries the meaning. The description adds no detail about whose UUID is expected or whether it must match the caller, leaving the baseline score for fully covered schemas.

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 opens with a specific verb and resource: 'Mine SHELL tokens.' That is unambiguous and clearly distinct from read-oriented siblings like balance, stats, or check_agent. It stops short of naming any alternative tool, so it does not reach full sibling differentiation.

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?

The definition supplies real usage conditions: a minimum trust score of 1 and a one-per-day cooldown, which tells an agent both when the call is permitted and how often. It does not explicitly route the agent to any alternative action when the trust requirement fails or the cooldown is active.

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