Skip to main content
Glama

trial_prove_wallet

Prove control of the account payer wallet (EIP-191 signature over the documented message); required before the free trial is consumed.

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": "trial_prove_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
signatureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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. It usefully discloses the signature scheme (EIP-191) and the gating effect on the trial, but leaves unstated whether this mutates/consumes state, whether it is idempotent, what happens on an invalid signature, and what a successful call returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One tight, front-loaded sentence with a parenthetical that supplies the mechanism, and the prerequisite clause last. Every element is relevant; only the dangling 'documented message' reference slightly weakens it.

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?

For a one-parameter, no-annotation, no-output-schema tool, the definition covers purpose and ordering but not the substance the agent actually needs: the exact message to sign, failure semantics, and whether the proof is per-wallet or per-session.

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 0% for the single parameter, so the description must compensate. It does add meaning by specifying the signature is EIP-191 over 'the documented message,' but that message is only referenced, never described, so the agent still lacks the exact payload to sign.

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?

States a specific verb and resource: proving control of the account payer wallet via an EIP-191 signature. That is clearly distinct from the sibling trial_* workflow tools (pairing, scoring, verdict), though it does not itself name or contrast any sibling.

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?

Gives an explicit precondition: it is 'required before the free trial is consumed,' which tells the agent where this call sits in the sequence. It does not state any when-not-to-use condition or what to do if the proof already exists, but the ordering guidance 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