Skip to main content
Glama

Doxtract

Set inbox webhook

set_inbox_webhook
Idempotent

Save where an inbox sends each parsed document, so documents that arrive by email or upload reach your system without a poll. Each body is signed with the returned secret. An empty url turns the webhook off. Only a key created by the workspace owner can change it.

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": {
      "inbox_id": "<inbox_id>",
      "url": "<url>"
    },
    "name": "set_inbox_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps URL to POST to. Empty turns the webhook off.
secretNoBasic auth password, or the bearer token.
headersNoExtra request headers.
inbox_idYesThe inbox id returned by create_inbox.
usernameNoBasic auth user name.
auth_typeNoHow the receiver is authenticated: "none", "basic" or "bearer". Defaults to "none".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety and idempotency, and the description usefully adds that bodies are signed with a returned secret, that an empty url disables delivery, and that only a workspace-owner-created key can change the setting. It does not clarify the relationship between the returned signing secret and the auth `secret` parameter, which is a real ambiguity for a mutation tool.

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?

Four short sentences, each carrying a distinct fact (purpose, signing, disable, authorization), with the purpose front-loaded and no redundant framing.

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?

Covers intent, delivery semantics, signing, disabling, and the authorization prerequisite for a six-parameter mutation with no output schema. The main residual gap is that the 'returned secret' is referenced without describing what the call returns or how it relates to the auth secret parameter.

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%, so all six parameters, including the auth_type enum and the maxItems headers array, are already documented in the schema; baseline 3 applies. The description adds only the disable-by-empty-url rule (already in the url field) and introduces 'returned secret', whose relation to the `secret` auth parameter is left unclear.

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 — saving the destination an inbox posts parsed documents to — plus the effect (delivery without polling). An agent can distinguish this from get_inbox/update_inbox/create_inbox because the description is about outbound delivery configuration, not inbox metadata.

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?

Clear when-to-use context: choose this when documents arrive by email or upload and you want push delivery rather than polling. It also gives the explicit off-condition (empty url). It does not name an alternative tool, so it stops short of full when/when-not routing.

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.