Skip to main content
Glama

Configure a completion webhook

talkform.configure_webhook
Destructive

Configures one HTTPS endpoint for completed handoffs in an authorized project. Replaces any active endpoint and returns the signing secret once. Requires handoffs:write permission. Optional projectId selects an owned OAuth account project.

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": {
      "url": "<url>"
    },
    "name": "talkform.configure_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
projectIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / projectId
      Added value: +{
      +  "format": "uuid",
      +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes beyond the annotations (destructiveHint, idempotentHint=false) by spelling out what actually gets destroyed ('replaces any active endpoint') and the notable side effect that the signing secret is returned only once. That one-time-secret detail is exactly the kind of behavior an agent cannot infer from the annotations or schema; it stops short of describing delivery failure/retry behavior.

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?

Three short sentences, zero waste, front-loaded with the action and its scope before permissions and optional-parameter detail. Every sentence adds information not available in the schema or annotations.

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 two-parameter write tool with no output schema, the description covers scope, destructive replacement, the one-time return value, and the auth requirement, which is enough to call it correctly. It omits any mention of sibling alternatives or what happens if the endpoint is unreachable/invalid, which keeps it from a 5.

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?

Schema description coverage is 0%, so the description must carry the load, and it does: 'url' is characterized as an HTTPS endpoint for completed handoffs (an HTTPS constraint the schema's generic 'uri' format does not enforce), and 'projectId' is explained as selecting an owned OAuth account project. Neither parameter's format limits (2048 chars, UUID pattern) are referenced, but the semantic role of both is covered.

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 gives a specific verb and resource: 'Configures one HTTPS endpoint for completed handoffs in an authorized project.' It is clearly distinct from get_webhook and delete_webhook by the 'configures' framing, though it never names those siblings explicitly to make the routing unambiguous.

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

Usage Guidelines3/5

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

'Requires handoffs:write permission' and 'Optional projectId selects an owned OAuth account project' state prerequisites and scoping, so the usage context is implied. There is no explicit when-to-use or when-not-to-use guidance relative to get_webhook, get_webhook/delete_webhook, or a handoff-creation flow.

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.