Skip to main content
Glama

Log of webhook deliveries

dosai_list_webhook_deliveries
Read-onlyIdempotent

The latest calls the project made to the owner's webhooks (up to 50, newest first): event, address without secrets, the answer code, attempts, duration and the error. Filter by integration_id (dosai_list_integrations) to see one webhook.

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": {
      "project_id": "<project_id>"
    },
    "name": "dosai_list_webhook_deliveries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows per page, max 50, default 20.
project_idYesFrom dosai_list_projects.
integration_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed2 schema fields changed
    • removedInput schema / properties / integration_id / pattern
      Removed value: -"^([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)$"
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([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)$"
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavior beyond them: hard cap of 50 rows, newest-first ordering, and the fact that the address is returned redacted ('without secrets'). It does not mention retention limits or whether the log is truncated historically, which is the main remaining gap.

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

Conciseness4/5

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

A single dense sentence plus a short filtering clause; the scope (latest, 50, newest first) is front-loaded before the returned columns. Nothing is redundant with the title, and the parenthetical dependency pointer is compact. It is slightly packed, but no sentence is wasted.

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?

With no output schema, the description usefully enumerates the returned fields, and the annotations cover the safety profile, so the essentials are present for a 3-parameter read tool. Gaps are modest: no statement of retention window, pagination behavior beyond the limit cap, or precedence versus the integration-failures sibling.

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 67%; limit and project_id already carry descriptions, and limit's 1-50 bounds and default are in the schema rather than the prose. The description does add meaning for the one undocumented parameter, integration_id, by explaining it filters to a single webhook and pointing to dosai_list_integrations for its value. That is useful compensation but not enough to exceed the baseline by much.

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?

States a specific verb and resource ('latest calls the project made to the owner's webhooks') plus scope constraints: up to 50 rows, newest first. It also enumerates the columns returned (event, address, answer code, attempts, duration, error), which makes the tool's output shape obvious. It does not differentiate itself from near-neighbours such as dosai_list_integration_failures or dosai_list_logs, which keeps it from a 5.

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?

The closing clause tells the agent how to narrow to a single webhook ('Filter by integration_id') and where to get that ID (dosai_list_integrations), which is genuine usage guidance. However, there is no statement of when to prefer this over the other log-style list tools, and no exclusions or caveats about when it is the wrong choice.

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