Skip to main content
Glama
Datris MCP Server

Datris MCP Server

update_tap

Modify an existing tap's configuration without regenerating its script: enable or disable it, set a CRON schedule, change the target pipeline, or edit the description.

Instructions

Update an existing tap's CONFIG without regenerating the script. Change the enabled state, CRON schedule, target pipeline, or description. USE THIS to set or adjust a tap's schedule (cron_expression) whenever the user describes a recurrence (nightly, daily, every morning, market open, etc.). The platform's scheduler runs the tap on the cadence you set — no external cron, Airflow DAG, or shell loop is needed (or wanted). See the SCHEDULING RULE in the server instructions. VALIDATION RULE: if you're enabling a cron_expression on a tap whose script has NEVER been validated, call test_tap FIRST and confirm it succeeds. The cadence-change path is safe for taps that have already run successfully; it is not safe to set a cron on a never-tested script. The platform enforces this: setting cron_expression on an untested script returns HTTP 409 with the remedy — save the tap without the cron, call test_tap until it succeeds, then call update_tap again with the cron. Cadence-only changes on a tap whose current script has passed test_tap are accepted. To change the SCRIPT itself, call create_tap again with the same name and the new script or instruction — create_tap upserts by name and replaces the existing script. There is no separate script-only update tool. If this Datris instance's agent policy requires a person to approve this action, the call does NOT perform it: it returns status pending_approval with an approvalId. Tell the user it is waiting for approval in Datris, then poll get_approval with that id (pause with wait_seconds between polls) — do not re-issue the action.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the tap to update
reasonNoOptional one-line reason for this change, recorded in the platform's audit log and shown to anyone asked to approve it.
sourceNoDeclared source identity for lineage/provenance (provider name or host). Pass an empty string to clear it and fall back to derivation.
enabledNoEnable or disable the tap
depends_onNoNames of other taps in the same catalog whose destination tables this tap reads. Replaces the declared list; pass an empty list to declare that it has none (overrides the platform's inference from the script). Omit to leave it unchanged. Orders and explains catalog_enable_order only; never enforced.
descriptionNoNew plain-English description
endpoint_urlNoFor HTTP taps only: new endpoint URL Datris POSTs the run context to. Rejected on Python taps.
cron_expressionNoQuartz CRON expression for recurring runs: 6 fields — seconds minutes hours day-of-month month day-of-week, plus an optional year (e.g., '0 0 * * * ?' for hourly, '0 30 5 ? * MON-FRI' for weekdays 5:30am). A 5-field Unix cron such as '*/1 * * * *' is NOT a Datris schedule: the save is refused with HTTP 400 whose `error` quotes the 6-field equivalent to resend. SET THIS whenever the user describes a recurrence — nightly, daily, hourly, market open, etc. The platform's scheduler fires the tap on this cadence automatically; do not propose external schedulers or shell cron for the user to run themselves.
target_pipelineNoNew target pipeline name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the HTTP 409 remedy for cron-on-untested-script, the HTTP 400 for 5-field Unix cron, and the approval-policy behavior (status pending_approval, approvalId, poll get_approval with wait_seconds, do not re-issue). These are non-obvious runtime behaviors an agent could not infer from the schema.

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?

Purpose and the scheduling mandate are front-loaded, and each block is purposeful. There is some redundancy — the 'no external cron/Airflow/shell loop' point is made twice and the cron guidance overlaps the parameter schema — plus an external pointer to a 'SCHEDULING RULE in the server instructions' that the agent may not have.

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 9-parameter mutation tool with no output schema, the definition covers the mutation surface, the validation prerequisite, the two error codes with remedies, the approval polling loop, and the sibling route for script changes. What remains (partial-update semantics, lineage fields) is already spelled out in the 100%-covered schema.

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 coverage is 100%, so all nine parameters are already documented, including the Quartz 6-field cron format and the 400 refusal. The description's parameter content largely restates the cron_expression schema entry rather than adding new meaning, and it says nothing about source, depends_on, endpoint_url, or reason. Baseline 3 applies when the schema does the work.

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 plus a crucial scope qualifier: 'Update an existing tap's CONFIG without regenerating the script.' It enumerates the mutable surface (enabled state, CRON schedule, target pipeline, description) and explicitly contrasts with create_tap for script changes, so an agent can distinguish it from siblings without reading any schema.

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 routing rules: use this for recurrence wording (nightly, daily, market open), use create_tap with the same name for script/instruction changes, and call test_tap first when enabling a cron on a never-validated script. It also names the alternative for the script path and states there is no separate script-only update tool.

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