Skip to main content
Glama

MaxRechnung

Webhook-Endpunkt abrufen

get_webhook
Read-only

Tarif: in jedem Tarif (Free, Pro, Business).

Webhook-Endpunkt abrufen

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": {
      "id": "<id>"
    },
    "name": "get_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPfad-Parameter id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered structurally. The description adds one genuine behavioral fact beyond annotations — that the endpoint is available on every plan (Free, Pro, Business) — which is useful entitlement context. It says nothing about what happens if the id does not exist or what the response contains, so it stays at the minimum.

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

Conciseness3/5

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

It is very short and front-loads the plan-tier note, but the second sentence merely repeats the title verbatim and therefore earns no place. Brevity here reflects under-specification rather than disciplined editing.

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

Completeness2/5

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

For a simple single-parameter read tool this could be adequate, but with no output schema the description should indicate what a webhook endpoint record contains or how a missing id is handled. Neither is present, leaving an agent with little more than the tool name.

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 description coverage is 100%, with the single required parameter documented as a UUID-formatted path parameter. The description adds no meaning beyond that, but with the schema fully documented, the baseline of 3 applies.

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

Purpose2/5

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

The only descriptive text is "Webhook-Endpunkt abrufen," which is a verbatim repeat of the title and name. It does identify the resource (a webhook endpoint) but adds nothing beyond the identifier, and it does not distinguish this from siblings such as delete_webhook or send_webhook_test.

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?

The description contains no when-to-use guidance, no prerequisites, and no reference to alternatives. The only context offered is plan availability, which says nothing about when an agent should call this versus another retrieval or webhook tool.

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