Skip to main content
Glama

delete_job

Remove a cron job from your norc account by specifying its ID. Use it to clear obsolete or unneeded scheduled jobs from chat.

Instructions

Delete a job.

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": "delete_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

D1.6/5.0
Behavior1/5

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

No annotations are provided, so the description bears full disclosure responsibility for a destructive mutation, yet it says nothing about permanence, cascading effects on runs, required permissions, or error behavior for a missing id. Only the word 'Delete' implicitly signals destruction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of padding, but its brevity reflects under-specification rather than disciplined conciseness. There is nothing to trim, yet nothing of substance is provided.

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

Completeness1/5

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

For a destructive tool with no annotations, no output schema, and 0% parameter coverage, the description supplies none of the information an agent needs to invoke it safely. It is not complete on any axis the structured fields leave open.

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 for the single parameter is 0%, and the description does not explain that 'id' identifies the job to remove or what format it takes. The only meaning conveyed is that the target is a job, which comes from the noun in the tool name rather than the description.

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

Purpose2/5

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

The description 'Delete a job' merely restates the tool name with no added specificity: it does not say what a job is, what deletion entails, or how it differs from siblings like delete_machine or update_job. An agent can infer the verb and resource, but nothing beyond the name itself.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives such as update_job or sync_jobs, no prerequisites, no warning about irreversibility, and no mention of what happens to associated runs. The definition offers no decision criteria at all.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.