Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Delimit Siem

delimit_siem

Configure and manage streaming of audit events to SIEM destinations such as Splunk, Datadog, EventBridge, or webhooks. Check status, test connectivity, or forward events.

Instructions

Manage SIEM streaming for audit-event forwarding (Splunk/Datadog/etc.).

When to use: to inspect or configure where Delimit's audit events stream — Splunk, Datadog, EventBridge, generic webhooks. When NOT to use: for one-shot notifications (use delimit_notify) or inbox handling (delimit_notify_inbox).

Sibling contrast: delimit_notify sends to humans; this configures structured-log streaming to SIEM endpoints.

Side effects: action="configure" / "forward" / "test" write to the configured SIEM endpoints (network calls). action="status" is read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventNoJSON string of an event (for forward / test).
actionNoOne of "status" (default), "configure", "test", "forward".status
enabledNo"true" or "false" (for configure).
settingsNoJSON string of settings (for configure).
integrationNoOne of "splunk", "datadog", "eventbridge", "webhook" (for configure).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv4.7.9
    • changedInput schema / properties / action / description
      Previous value: -"status, configure, test, or forward"New value: +"One of \"status\" (default), \"configure\", \"test\", \"forward\"."
    • changedInput schema / properties / enabled / description
      Previous value: -"\"true\" or \"false\" to enable/disable (for configure)"New value: +"\"true\" or \"false\" (for configure)."
    • changedInput schema / properties / event / description
      Previous value: -"JSON string of event to forward (for forward/test)"New value: +"JSON string of an event (for forward / test)."
    • changedInput schema / properties / integration / description
      Previous value: -"splunk, datadog, eventbridge, or webhook (for configure)"New value: +"One of \"splunk\", \"datadog\", \"eventbridge\", \"webhook\" (for configure)."
    • changedInput schema / properties / settings / description
      Previous value: -"JSON string of settings to update (for configure)"New value: +"JSON string of settings (for configure)."
  2. Addedv4.5.5

TDQS

A4.7/5.0
Behavior5/5

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

The description explicitly discloses action-dependent side effects: configure/forward/test write to SIEM endpoints via network calls, while status is read-only. This adds behavior beyond the readOnlyHint=false annotation and gives the agent a clear safety/impact model.

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 front-loaded with the core purpose and uses labeled sections for use, exclusion, sibling contrast, and side effects. It is compact with no redundant sentences.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists, the rich schema descriptions for all 5 optional parameters, and the annotations, the description covers purpose, exclusions, alternative tools, and side effects. Nothing critical for an agent to select and invoke the tool correctly is missing.

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% and each parameter is already documented in the input schema. The description reinforces that actions have side effects but does not add new parameter-level semantics beyond what the schema provides, so baseline 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?

States a specific verb and resource: managing SIEM streaming for audit-event forwarding, naming Splunk/Datadog/EventBridge/webhooks. It also differentiates itself from delimit_notify and delimit_notify_inbox, so an agent can distinguish it from nearby siblings.

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

Usage Guidelines5/5

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

Gives explicit 'When to use' and 'When NOT to use' guidance with named alternatives (delimit_notify for one-shot notifications, delimit_notify_inbox for inbox handling). The sibling contrast further clarifies when this tool is the right choice: structured-log streaming vs human notifications.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/delimit-ai/delimit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server