Skip to main content
Glama

Test a Network webhook

test_network_webhook

Sends a test change to a subscription's receiver URL to verify the endpoint and signature check before real events arrive; requires a write-scope API key.

Instructions

Send the latest matching change to the subscription's URL now, marked "test": true, to check the receiver and its signature check before anything real arrives. Needs a write-scope API key.

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

Input Schema

NameRequiredDescriptionDefault
idYesSubscription id (publicId)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that a live HTTP delivery to the external URL occurs immediately, that the payload is tagged test:true so receivers can discriminate, and that a write-scope API key is required. It does not cover return value, delivery-failure behavior, or whether the test hit appears in delivery history.

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?

Two sentences, zero waste, front-loaded with the action and the key qualifier (test:true), then the rationale, then the auth prerequisite. Every clause earns its place.

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 one-parameter side-effecting tool with no annotations or output schema, the description covers action, marker semantics, purpose, and auth requirement. The remaining gap is the response: with no output schema, an agent cannot tell whether the call reports delivery success or signature-check results.

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 coverage is 100% and the sole parameter is documented as the subscription publicId, so the schema already does the explanatory work. The description adds only the linkage that the id determines which subscription URL gets the test delivery; baseline 3 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?

The description gives a precise verb and object: send the latest matching change to the subscription's URL now, flagged with "test": true. The "test" marker and the "before anything real arrives" framing make it unmistakably a trial delivery distinct from a real subscription delivery or the subscribe/unsubscribe siblings.

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 states the occasion clearly: use it to check the receiver and its signature check before real events flow. It does not name an alternative tool or explicitly exclude cases (e.g., after the endpoint is already verified, or when no changes match), so it stops short of a full when/when-not map.

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