Skip to main content
Glama

thanaton_manage_log_drains

List, add, or delete external SIEM log drains for Datadog, Papertrail, Axiom, and HTTPS webhooks to route project logs to your monitoring stack.

Instructions

List, configure, or remove external SIEM log drains (Datadog, Papertrail, Axiom, HTTPS Webhooks).

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>",
      "action": "<action>"
    },
    "name": "thanaton_manage_log_drains"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoHTTPS or syslog destination URL (required for add)
nameNoDrain name / label
actionYesAction to perform
drain_idNoDrain ID (required for delete)
providerNoSIEM provider
batch_sizeNoFlush batch size (default: 100)
project_idYesTarget project ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses almost nothing behavioral: no permissions or auth requirements, no statement that 'delete' is destructive and irreversible, no rate-limit or flush-timing notes even though batch_size is exposed. The parenthetical provider list is the only added context.

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?

One front-loaded sentence with zero filler, listing the verb set before the resource and provider scope. It is efficient, though its brevity is part of why behavioral context is missing.

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?

This is a multi-action tool containing a destructive operation, with seven parameters, no annotations, and no output schema. The description never explains what a list response contains, what add returns (drain ID?), or that delete is permanent, which is inadequate for this complexity.

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 the schema already documents every parameter including per-action requirements (url for add, drain_id for delete) and the batch_size default. The description adds nothing beyond restating the provider names that already appear in the provider enum; baseline 3 applies.

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 set (list, configure, remove) and resource (external SIEM log drains), and names the supported providers (Datadog, Papertrail, Axiom, HTTPS Webhooks) so an agent can immediately tell what system this touches. It does not differentiate from sibling tools like thanaton_get_logs, and 'configure' loosely maps to the schema's 'add' action rather than being a real action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to choose this over thanaton_get_logs or other log-related siblings, and no prerequisites or exclusions. The only routing signal is the action enum in the schema, which is structured data rather than description content.

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