Skip to main content
Glama
delega-dev

delega-mcp

by delega-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_ingress_source

Update an inbound connector source (admin only) for hosted ingress, changing only supplied fields and optionally rotating its signing secret.

Instructions

Update an inbound connector source (admin only). Only supplied fields change; pass rotate_secret true to mint a new signing secret (shown once — the old secret stops working immediately). Hosted API only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew source name
activeNoEnable or disable the source
filtersNoReplacement filters (full replacement, not a merge)
templateNoMaps payload paths to task fields — a closed vocabulary, no expressions
source_idYesIngress source ID to update
rotate_secretNoMint a new signing secret; the old one stops working immediately
default_project_idNoNew pinned project (null clears)
default_assignee_agent_idNoNew pinned assignee (null clears)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.19.0
    • removedInput schema / properties / default_assignee_agent_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / default_assignee_agent_id / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / default_project_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / default_project_id / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / filters / items / properties / value / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  }
-]
    • addedInput schema / properties / filters / items / properties / value / type
      Added value: +[
+  "string",
+  "number",
+  "boolean"
+]
    • removedInput schema / properties / source_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / source_id / type
      Added value: +[
+  "string",
+  "number"
+]
  2. Addedv1.18.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and performs well: partial-update semantics ('only supplied fields change'), secret rotation behavior ('shown once — old secret stops working immediately'), and admin/hosted constraints. It omits any statement about the response shape beyond the one-time secret display, which is the main remaining gap.

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?

Three compact sentences, front-loaded with the action and scope, then the mutation contract and the destructive rotate_secret consequence. No redundant phrasing and every clause carries information.

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?

For a mutation tool with no annotations and no output schema, the description covers partial update, secret rotation irreversibility, and environment/auth constraints. It could note what the response returns besides the one-time secret, but is otherwise complete for correct invocation.

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 all 8 parameters are already documented in the schema. The description reinforces the partial-update contract and the one-time secret reveal, but adds little that the schema does not already state, so the baseline 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?

States a specific verb (update) and resource (inbound connector source) plus scope qualifiers (admin only, Hosted API only). This cleanly separates it from the create/delete/list_ingress_source siblings without needing to name them.

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?

Gives clear preconditions — admin only and Hosted API only — so the agent knows the required auth and environment context. It does not explicitly name alternatives or when-not-to-use, but for an update operation against an existing source the context is unambiguous.

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