Skip to main content
Glama
Jackxiaozhiren

datasentry

by Jackxiaozhiren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

job_update

Destructive

Modify a scheduled data-quality job's enabled state, cron, retry attempts, webhook URL, or quality gate threshold. Changing cron recalculates the next run time and returns the updated job view.

Instructions

Update a scheduled job (Step 88, ADR-088): enabled/cron/retry_attempts/webhook_url/gate_quality_min, partial update; cron change recomputes next run time. Returns the updated view.

Input Schema

NameRequiredDescriptionDefault
cronNo5-field cron, e.g. '0 9 * * *'
job_idYes
confirmYesmandatory acknowledgement that this call mutates state; the tool writes nothing unless it is true (D5-08, D5-12)
enabledNo
webhook_urlNo
retry_attemptsNo
gate_quality_minNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "mandatory acknowledgement that this call mutates state; the tool writes nothing unless it is true (D5-08, D5-12)",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "job_id"
-]New value: +[
+  "job_id",
+  "confirm"
+]
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag this as a non-readOnly, destructive mutation, and the description adds genuinely useful behavior: updates are partial, and a cron change recomputes the next run time. It also notes the response is the updated view, though it says nothing about permissions or reversibility.

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 dense sentence that front-loads the verb and resource, then the field set, then the side effect and return value. The ADR/Step citation is arguably noise but small; no sentence is wasted.

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 7-parameter destructive mutation with no output schema, the description covers scope, partial-update semantics, a key side effect, and the return shape. The remaining gap is auth/permission requirements and whether the mutation is reversible.

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 only 29%, so the description must compensate and it does partially by enumerating the five updatable fields (enabled/cron/retry_attempts/webhook_url/gate_quality_min). However, it adds no per-parameter semantics such as value ranges for gate_quality_min or expected webhook_url format, so it mostly restates property names.

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?

Specific verb (update) plus a specific resource (scheduled job), with the mutable field set enumerated. It is clearly distinguishable from siblings like job_create, job_trigger, and job_remove.

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

Usage Guidelines3/5

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

States 'partial update' and lists which fields can be changed, which implies the editing context, but it names no alternatives and gives no when-not guidance (e.g. versus job_trigger for forcing a run or job_remove for deletion).

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