Skip to main content
Glama

submit_crypto_approval_token

Submit a human supervisor's approval challenge token to finalize and broadcast a high-value on-chain transaction after anti-drainer checks.

Instructions

Submit an approval challenge token granted by the human supervisor to finalize and broadcast a high-value on-chain transaction.

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": {
      "challengeToken": "<challengeToken>"
    },
    "name": "submit_crypto_approval_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
challengeTokenYesThe cryptographic challenge token (CRYPTO_AUTH_...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the key trait that this action irreversibly broadcasts an on-chain transaction. However, it omits token lifetime/single-use semantics, failure behavior for invalid or expired tokens, and permission requirements, which matter a lot for an irreversible 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?

A single front-loaded sentence with zero filler that names the input, the actor, and the resulting action. Nothing is redundant or padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required string parameter) and the description explains the trigger and effect, but with no output schema it never says what a successful submission returns (e.g., a transaction hash) or what an error looks like. Adding a clause on the result and on token invalidation would complete it.

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 description coverage is 100%, so the baseline is 3; the schema already defines challengeToken and its CRYPTO_AUTH_ prefix format. The description only adds provenance ('granted by the human supervisor'), no validation, format, or expiry semantics.

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?

Specific verb ('Submit') plus specific resource ('approval challenge token') and an explicit outcome ('finalize and broadcast a high-value on-chain transaction'). The purpose is clearly distinct from siblings like transfer_crypto or get_crypto_security_status, though no sibling is named to route the agent explicitly.

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 phrase 'token granted by the human supervisor' implies the prerequisite for calling it (a human-in-the-loop approval step), so usage is implied rather than stated. There is no guidance on what to do if no token exists, whether the token is single-use or expires, or which sibling to call instead when the transaction is not high-value.

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