@illodev/taiga-mcp

taiga_webhooklogs_get

Retrieve a Taiga webhook log entry by ID to inspect its request, response, and delivery status.

Instructions

Get a webhook log entry by ID.

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": {
      "id": "<id>"
    },
    "name": "taiga_webhooklogs_get"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Webhook log ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden of indicating safety. 'Get' clearly implies a read-only operation, but the description does not disclose any details about the response format, error behavior, or required permissions. For a simple retrieval tool, this is acceptable but not rich in behavioral context.

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?

The description is a single, direct sentence with no filler or redundant information. Every word contributes to the meaning, making it an exemplary model of conciseness.

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?

Given the simplicity of a get-by-id operation with one parameter and no output schema, the description suffices to convey the core functionality. It could be enhanced by specifying the structure of a webhook log entry or common use cases, but the tool's simplicity and the clear 'Get a webhook log entry' phrasing make the context reasonably complete.

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?

The input schema already describes the single parameter 'id' as 'Webhook log ID' with 100% coverage. The description adds no additional semantic detail, merely restating that the lookup is by ID. Since the schema is fully self-explanatory, a baseline score of 3 is appropriate.

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?

The description 'Get a webhook log entry by ID' uses a specific verb ('Get') and clearly identifies the resource ('webhook log entry') and the selector ('by ID'). It unambiguously distinguishes this from sibling tools like taiga_webhooklogs_list or taiga_webhooklogs_resend, making the tool's purpose immediately clear.

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 that this tool is used when you have a specific webhook log ID and want a single entry, but it does not explicitly mention alternatives or when not to use it. No contrast is given with the similar list or resend tools, so the guidance is only implied by the 'by ID' phrasing.

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

Deploy Server