Skip to main content
Glama

Job queue

idrac_list_jobs
Read-onlyIdempotent

List iDRAC job queue entries for BIOS/RAID configuration, firmware updates, and exports with state and progress, or retrieve one job by ID to track server tasks.

Instructions

List the iDRAC job queue (BIOS and RAID configuration jobs, firmware updates, exports) with state and progress, or get one job by id.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of jobs to return (newest first).
stateNoOnly jobs in this state, e.g. Scheduled, Running, Completed, Failed.
job_idNoA specific job id such as JID_123456789012.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so the safety profile is covered. The description adds that results carry state and progress, but says nothing about ordering, pagination behavior, or what happens when job_id is invalid/absent.

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?

A single front-loaded sentence covering both modes with no filler. Slightly dense — the parenthetical list could read as scope detail rather than example — but 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?

For a simple read-only list tool with a fully described 3-parameter schema and annotations covering safety, this is nearly sufficient; the added 'state and progress' note tells the agent what fields matter. Only pagination/ordering and error behavior are left unstated.

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 100%, so limit, state and job_id are already fully documented in the schema. The description only hints at the state and job_id modes without adding format or interaction details beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('List the iDRAC job queue') and enumerates the job categories it covers (BIOS/RAID config, firmware updates, exports). No sibling tool touches jobs, so the agent can place it instantly.

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 'or get one job by id' clause implies the two modes, so the agent can infer list vs. single-fetch usage. It does not say when to prefer this over alternatives (e.g. logs) or note any prerequisites, leaving usage only implied.

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