Skip to main content
Glama
Sign In
BeeL MCP server

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_test_webhook_subscription

DestructiveIdempotent

Sends a synthetic signed webhook payload immediately to verify your endpoint is reachable and handles deliveries and signature checks before relying on real events.

Instructions

Sends a synthetic payload to the subscription's URL immediately, outside the normal delivery queue. Use it to verify that your endpoint is reachable and handles deliveries correctly before you rely on real events.

  • Payload: carries "test": true and synthetic data, and is signed like any other delivery, so it also exercises your signature check.

  • Retries: none. A failed test is not retried and does not appear in the delivery history.

  • Idempotency-Key: repeating the call with the same key returns the cached result without sending the test payload again.

  • Result: read delivery_success; a delivery your endpoint rejected is still a successful test run, not an error.

BeeL API endpoint: POST /v1/accounts/{account_id}/webhooks/{webhook_id}/test (reference: https://docs.beel.es)

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": {
      "account_id": "<account_id>",
      "webhook_id": "<webhook_id>"
    },
    "name": "beel_test_webhook_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesYour own account, or an account you provisioned. It — not the credential, and not the `BeeL-Active-Company` header — decides which account the operation acts on. An account you do not reach answers `403`, and so does an account that does not exist, so the existence of somebody else's account is never disclosed.
webhook_idYesSubscription of the account in the path. A subscription of another account answers `404`, the same as one that does not exist: under the account resolved from `{account_id}` it simply is not there.
idempotency_keyNoOptional idempotency key for this operation. Omit it and one is derived from the request itself, which makes a blind retry safe but also collapses a SECOND, deliberately identical operation into the first for 24 hours. Set it — to an order id, or anything unique per intended operation — whenever you mean to create something that may look identical to what you just created.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.3.1

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: no retries, failures excluded from delivery history, payload is signed so signature checks are exercised, and idempotency keys return a cached result for repeats. Annotations only flag readOnly=false, destructive=true and openWorld=true; the description explains what the side effect actually is and what it does not touch.

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?

Front-loaded purpose sentence followed by four tight bullets covering payload, retries, idempotency and result reading. Each bullet carries distinct, decision-relevant information with no filler.

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

Completeness5/5

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

No output schema exists, yet the description tells the agent exactly which field to read (delivery_success) and that a rejected delivery is a successful test run rather than an error. Combined with the retry/history caveats, an agent has everything needed to call and interpret this correctly.

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 account_id, webhook_id and idempotency_key are all documented in-schema. The description only adds that the target is the subscription's URL and restates the idempotency caching behavior in behavioral terms; it introduces no new parameter syntax or constraints.

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: sends a synthetic test payload to a subscription's URL immediately, outside the normal delivery queue. That phrasing separates it from beel_retry_webhook_delivery (real delivery retry) and beel_list_webhook_deliveries without opening either schema.

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?

Gives an explicit when-to-use: verify the endpoint is reachable and handles deliveries correctly before relying on real events. It doesn't name a sibling alternative or state a when-not (e.g., use retry instead when a real delivery failed), so it stops short of full routing guidance.

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

Deploy Server

Other Tools