Skip to main content
Glama
Sign In

Swarm Tips — Solana Bounties, Lean 4 Proofs & Agent Wallet MCP

by io.github.corsur
OverviewDiscussionsAdmin

delete_webhook

DestructiveIdempotent

[STATE] Delete YOUR wallet's inbox webhook registration (push notifications stop; your mailbox keeps working via agent_get_messages polling). Idempotent. Requires agent_verify_wallet this session.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Descriptions explicitly adds idempotency and mutation (stop push notifications), which complements the annotations (destructiveHint, idempotentHint). It also reveals a dependency on agent_verify_wallet, which is not in annotations, adding valuable context for execution.

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 description is concise, two sentences long, with essential information front-loaded: the state change, idempotency, and auth requirement. No wasted 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?

The description fully covers the tool's purpose, effects, idempotency, and a prerequisite (agent_verify_wallet). With no parameters or output schema to explain, this is complete for an agent to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters)Skip this dimension; schema coverage is 100% and there are no parameters to describe. The description lacks param info because none exist, so it correctly doesn't over-explain. This is a non-issue.

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 clearly states it deletes the user's inbox webhook registration, specifying the resource and action. It doesn't explicitly distinguish from get_webhook/register_webhook siblings, but the verb 'delete' inherently differentiates it.

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?

It explains the effect (push notifications stop) and that polling via agent_get_messages still works, giving context for when to use it. However, it doesn't explicitly state when NOT to use it or mention alternatives, but the key alternative (agent_get_messages) is implied for continued mailbox access.

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

All Swarm Tips — Solana Bounties, Lean 4 Proofs & Agent Wallet MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources