Skip to main content
Glama

list_webhooks

Read-only

The coach's outbound webhooks: URL, subscribed events, on/off, last delivery status.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description then adds real value beyond the annotations by disclosing the shape of what comes back: endpoint URL, subscribed event types, enabled/disabled state, and last delivery status, which is important because no output schema exists. It stops short of saying whether disabled webhooks are included or how results are ordered or paginated.

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?

A single compact fragment with no filler, and the most identifying information (whose webhooks, what kind) is front-loaded. The colon-and-list construction reads as a field inventory rather than a complete sentence, which is slightly abrupt but very efficient.

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

Completeness4/5

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

For a zero-parameter read tool with no output schema, the description covers the essentials: what is listed, whose it is, and what each entry contains. Only minor operational details are absent, such as result count, ordering, and whether disabled webhooks appear.

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; the baseline for a parameterless schema applies. No misleading parameter hints are present.

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 names a specific resource ('the coach's outbound webhooks') and enumerates the fields returned (URL, subscribed events, on/off, last delivery status), so an agent knows exactly what this tool surfaces. It is a noun phrase rather than a verb phrase, and it does not explicitly contrast with any sibling, but no sibling in the visible catalog deals with webhooks, so the risk of confusion is low.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The 'coach's' qualifier implies the scope is the caller's own webhook configuration rather than some other tenant's, but that has to be inferred rather than 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.