Skip to main content
Glama
Jackxiaozhiren

datasentry

by Jackxiaozhiren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

job_trigger

Immediately run a scheduled data-quality job once by job ID. Requires confirm=true, returns run ID and outcome, and blocks duplicate runs with a 409-style error if already running.

Instructions

Immediately run a scheduled job once (Step 51). Returns the run id and outcome; mutual exclusion: 409-style error if already running.

Input Schema

NameRequiredDescriptionDefault
job_idYes
confirmYesmandatory acknowledgement that this call mutates state; the tool writes nothing unless it is true (D5-08, D5-12)

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.5/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, openWorld=true, so the concurrency constraint ('409-style error if already running') and the return shape ('run id and outcome') are genuine value-adds beyond structured fields. It could say more about what happens to an in-flight run, but this is solid disclosure for a mutation tool.

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?

Front-loaded with the action and kept to two tight clauses. The '(Step 51)' reference is internal noise that doesn't help an agent, but otherwise nothing 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?

With no output schema, the description correctly covers return values ('run id and outcome') and the concurrency failure mode. For a 2-parameter mutation tool this is largely complete, though the undocumented job_id and vague 'outcome' leave minor gaps.

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

Parameters2/5

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

Schema coverage is only 50%: 'confirm' is well documented in the schema itself, but 'job_id' is undocumented in both schema and description. The description does not compensate for that gap, adding no meaning about how job_id is obtained or formatted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Immediately run a scheduled job once.' This is clearly distinct from jobs_list (read) and job_create/update/remove (lifecycle management). However, it never names a sibling or explicitly contrasts itself, so it stops short of full differentiation.

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?

The word 'Immediately' and 'once' imply on-demand single execution versus scheduled recurrence, and the 409 mutual-exclusion note gives a precondition. But there is no explicit 'use this when / use X instead' guidance, so usage is only implied.

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