Skip to main content
Glama

job_setRetries

Set the retry count for a failed job to reset retries after fixing the root cause and re-enable execution.

Instructions

Set the retry count for a failed job. Use to reset retries after fixing the root cause of a job failure. Set to 1 or more to re-enable execution.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.0
    • addedInput schema / additionalProperties
      Added value: +{}
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "id"
      +]
  2. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the key effect that a value of 1 or more re-enables execution. However, it omits what happens at 0 (presumably execution stays disabled), whether the change is reversible, what permissions are required, and what the call returns on success.

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?

Three short sentences, front-loaded with the action and effect, with no filler. The only minor redundancy is the overlap between 'reset retries' and 'set to 1 or more to re-enable execution'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with zero annotation coverage, no output schema, and no documented parameters, the definition covers the intent but not the mechanics. An agent still cannot tell from the description how the retry count is supplied or what a value of 0 does.

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 description coverage is 0% with one parameter, so the description must compensate, yet it never explains that 'id' is the job identifier. Worse, the retry count value itself is absent from the input schema while the description talks about setting it to '1 or more', leaving the caller's expected payload ambiguous.

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?

The first sentence names a specific verb and resource ('Set the retry count for a failed job'), which cleanly separates it from siblings like job_setSuspension or job_triggerExecution. It does not explicitly name an alternative tool, but the resource-level specificity is enough for an agent to identify it.

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?

'Use to reset retries after fixing the root cause of a job failure' gives a clear situational trigger, and 'Set to 1 or more to re-enable execution' adds an operational condition. There is no when-not guidance (e.g., when the job has not failed, or when a suspension tool is the better route), which keeps it short of a 5.

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