Skip to main content
Glama
presign-guard-wallet-mcp

presign-guard-wallet-mcp

Send feedback to Fizzl (free)

feedback

Report missing wallet capabilities, broken flows, limits, or payment errors to Fizzl so a person can review the issue; no keys or personal data required.

Instructions

Tell Fizzl what is missing or broken in this wallet: a network or coin an API asks for that the wallet can't pay, a kind of service you couldn't find, a limit or step that gets in the way, or a bug. Free, and it costs your user nothing. A person at Fizzl reads every report; nothing in it is run or changed automatically. Never put keys, passwords or your user's personal data in it. If it is about a payment that went wrong (paid but no answer, a wrong answer), add payment with its tx (the settlement transaction from the pay answer) and network, and the wallet server, when this wallet is linked to one, adds your own receipt for it to the report.

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": {
      "message": "<message>"
    },
    "name": "feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNobug, feature (something missing) or other
contactNoOptional: how to reach you about it
messageYesWhat happened or what you need
paymentNoOptional: the payment it is about, when a paid call went wrong
endpointNoOptional: the tool, API or route it is about, e.g. pay_x402

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.7

TDQS

A4.4/5.0
Behavior4/5

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

The only annotation is openWorldHint=true, so the description carries most of the load and does so well: it discloses that a human at Fizzl reads every report, that nothing is executed or changed automatically (no wallet side effects), and that keys/passwords/personal data must never be included. It does not say what the caller gets back on success, nor any rate limit, which keeps it at 4.

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?

Front-loaded with the purpose and free of filler; each sentence adds scope, safety, or payment-attachment detail. The second half is a long run-on sentence covering the payment branch, which slightly hurts scanability but does not waste words.

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

Completeness5/5

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

For a 5-parameter tool with a nested payment object, no output schema, and a single openWorldHint annotation, the description covers purpose, triggering conditions, safety constraints, and the conditional nested-object usage. What remains (type/contact/endpoint field meaning) is fully documented in the schema itself.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond it: 'payment' is tied to a failed paid call, tx is identified as 'the settlement transaction from the pay answer', and the agent is told the wallet server fills in its own receipt when linked to one — behavior not inferable from the nested schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Tell Fizzl what is missing or broken in this wallet', followed by a concrete enumeration of the reportable cases (unsupported network/coin, missing service, blocking limit, bug). This is clearly distinguishable from the money-moving siblings (send_native, pay_x402, buy_usdc) and the read-only ones (wallet_status, find_services).

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 rich positive guidance on when to use it, including the four categories of report and a conditional branch: if the issue is a payment that went wrong, attach 'payment' with tx and network. It also states the cost condition ('Free, and it costs your user nothing'), which affects the agent's decision to use it. It does not name an alternative channel or state when not to file a report, so it falls short of the 5 bar.

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