Skip to main content
Glama

db_webhook_get

Read-onlyIdempotent

Return the current database change-webhook registration for a project (url, events, secret, last delivery status). Returns { webhook: null } when none is set.

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

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds real value beyond that by disclosing the response shape and, importantly, the `{ webhook: null }` sentinel for the unset case, which prevents misinterpretation of an empty result. It stops short of noting that a secret is exposed in plaintext or any auth requirements.

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 tight sentences with zero waste: the operation and returned fields come first, the null-case edge is appended. Nothing is redundant or buried.

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 steps in to describe the return payload and the empty case, which is the main thing an agent needs for a one-parameter read tool. Minor gaps remain (whether the secret is masked, whether the call errors for unknown projects), but nothing blocking.

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 single project_id parameter is thoroughly documented in the schema itself (UUID/subdomain/slug, 'default' fallback, multi-project error behavior). The description adds nothing about the parameter, which is acceptable given the schema carries that load — baseline 3.

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 ('Return the current database change-webhook registration for a project') and even enumerates the returned fields (url, events, secret, last delivery status). An agent knows exactly what this retrieves without opening the schema.

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?

Usage is only implied by the word 'current' — it reads as a fetch operation, and the null-return case tells the agent how to interpret an unconfigured project. There is no explicit when-to-use framing, no mention of related operations, and no prerequisites stated.

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