Skip to main content
Glama
Sign In
NomaCMS MCP Server

NomaCMS MCP Server

Official
by NomaCMS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Webhook Logs

list_webhook_logs

Retrieve delivery logs for any webhook to monitor its performance and troubleshoot failed deliveries.

Instructions

List delivery logs for a 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": {
      "uuid": "<uuid>"
    },
    "name": "list_webhook_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
uuidYesWebhook UUID
paginateNoItems per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are present, so the description carries full burden. It does not disclose pagination behavior, ordering, or what constitutes a 'delivery log'. The schema reveals pagination params but the description adds no behavioral context beyond the action.

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 sentence that is front-loaded and efficient. Could potentially add a bit more guidance (e.g., about pagination defaults) without harming conciseness.

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

Completeness2/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 should clarify return format (e.g., array of logs, pagination info). It does not, leaving the agent with incomplete context for a listing tool.

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 description coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema's scope, merely restating the tool's function.

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?

Description clearly states the action 'List' and the resource 'delivery logs for a webhook'. It distinguishes from sibling tools like list_webhooks (which lists webhooks themselves) and get_webhook (which retrieves a single webhook).

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 description implies usage for retrieving logs for a specific webhook via the required uuid parameter. However, it provides no explicit guidance on when to use this tool versus alternatives, or any exclusions.

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