Skip to main content
Glama

create_ingress_source

Create a signed endpoint that converts external events into Delega tasks with HMAC validation, filters, and pinned routing.

Instructions

Create an inbound connector: a signed public endpoint that turns external events (CI failures, alerts, calendars) into Delega tasks (admin only). The sender signs each POST body with HMAC-SHA256 (header X-Delega-Ingress-Signature: t=,v1=<hex of HMAC(secret, 't.body')>, 5-minute tolerance). Ingress can ONLY create tasks; routing (project/assignee) is pinned here and never payload-controlled; every created task carries the 'ingress' label and provenance marker, and automation rules ignore ingress tasks unless they explicitly opt in with a source=ingress condition. Hosted API only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesShort human-readable source name, e.g. 'github-actions-ci'
activeNoSet false to create the source disabled
filtersNoOnly deliveries passing all filters create tasks
templateYesMaps payload paths to task fields — a closed vocabulary, no expressions
default_project_idNoProject for created tasks (pinned; payload cannot override)
default_assignee_agent_idNoAssignee for created tasks (pinned; payload cannot override)
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: HMAC-SHA256 signature, 5-minute tolerance, task-only creation, pinned routing, ingress labels, automation rule opt-in, and hosted API restriction. No contradictions found.

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?

The description is lengthy but every sentence adds value, covering authentication, constraints, and behavior. It is front-loaded with the main purpose, though some structure like bullet points could improve readability slightly.

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?

For a tool with 6 parameters, no output schema, and no annotations, the description is remarkably complete. It explains authentication, routing, automation rules, and provenance, leaving few gaps about what the tool does and its implications.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant meaning beyond the schema, such as explaining the closed vocabulary for templates, the AND logic for filters, and the pinning of project/assignee. This enhances understanding beyond the schema's descriptions.

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 clearly states it creates an inbound connector that turns external events into tasks, specifying the resource and its function. It distinguishes from siblings like create_webhook and create_task by focusing on signed endpoints and pinned routing.

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

Usage Guidelines4/5

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

The description indicates admin-only usage, explains the mechanics of signing and routing, and notes automation rules. While it lacks explicit comparisons to alternative tools, the context of when to use this for setting up external event pipelines is clear.

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/delega-dev/delega-mcp'

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