Skip to main content
Glama
Sign In
resolve-mcp

resolve-mcp

by irstone-source
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

render_job_delete

Delete a specific render job by its ID or remove all pending jobs from the queue to manage rendering tasks.

Instructions

Delete one render job by id, or the whole queue with all_jobs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "render_job_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNo
all_jobsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It mentions 'delete' but does not disclose whether the action is irreversible, whether it cancels running jobs, or any side effects. This lack of detail is a significant gap for a destructive operation.

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?

The description is extremely concise, using a single sentence to cover the main functionality. It is front-loaded with the action and resource. Minor improvement could be to list the parameters explicitly, but it remains efficient and clear.

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

Completeness2/5

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

Given no output schema and no annotations, the description is incomplete. It lacks information about return values, error handling, prerequisites (e.g., must a job be stopped first?), and confirmation prompts. For a destructive tool with two parameters, more context is needed for safe usage.

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 0%, so the description must compensate. It adds some meaning by explaining that 'job_id' identifies a single job and 'all_jobs' deletes the whole queue. However, it does not detail the types (string, boolean) or behaviors (e.g., required vs optional), which are partly in the schema. The added value is moderate.

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?

The description clearly states the action ('delete') and the resource ('render job'), distinguishing between deleting a single job by ID and deleting the entire queue with the 'all_jobs' flag. This provides a specific verb+resource meaning and differentiates from sibling tools like 'render_job_add' or 'render_stop'.

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

Usage Guidelines2/5

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

The description does not provide guidance on when to use this tool versus alternatives, such as stopping a render job without deleting it. It lacks context on prerequisites or when not to use it, leaving the agent to infer usage from the name alone.

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