Skip to main content
Glama

get_webhook

Read-onlyIdempotent

[READ] Read YOUR wallet's registered inbox webhook: url, verified state, hmac_secret_sha256 (fingerprint of the hmac_secret returned once at register_webhook; raw secret is redacted on reads — re-call register_webhook to rotate), consecutive delivery failures, and disabled/last-delivery timestamps. Returns registered:false if none. 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": "get_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?

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantive behavior: the raw hmac_secret is redacted on reads and only a sha256 fingerprint is returned, rotation requires re-invoking register_webhook, and an unregistered wallet yields registered:false rather than an error. These are non-obvious result-shape facts an agent cannot get from the annotations.

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 read/wallet framing and the returned field list, with the auth requirement last. The hmac parenthetical is long but every clause carries information; nothing is filler, though the sentence is dense enough to be a single heavy block.

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?

There is no output schema, so the description carries the return-value burden entirely and does so by listing the returned fields and the unregistered-wallet case. Auth prerequisite and secret-redaction behavior are both covered, leaving no material gap for a zero-parameter read.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the schema shows. Baseline of 4 applies.

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 with explicit scope: "Read YOUR wallet's registered inbox webhook," then enumerates exactly what comes back (url, verified state, hmac fingerprint, failure count, timestamps). The [READ] tag and the "YOUR wallet" scoping make it immediately distinguishable from register_webhook or delete_webhook without consulting another schema.

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 a concrete precondition ("Requires agent_verify_wallet this session") and names the sibling to use for the adjacent action ("re-call register_webhook to rotate"). It does not state a when-not-to-use case, but the usage context is unambiguous for a single-resource read.

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