Skip to main content
Glama

Com List Jobs

com_list_jobs
Read-onlyIdempotent

List recent COM jobs with their state and result to track firmware updates, inventory collection, power tasks, and OneView sync; filter by job state, account, or limit.

Instructions

Newest COM jobs (firmware updates, inventory collection, power, OneView sync, ...) with state and result.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
stateNoOnly jobs in this state.
accountNoCOM account name from list_servers; omit to use the first one.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower. The description adds that results are ordered newest-first and include state and result fields, which is genuine value. It does not say whether the list is truncated by a default window, how pagination works, or what happens when no account is given (the schema carries that last point).

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?

One short sentence with the key noun and the ordering up front, then illustrative examples. The trailing "..." is a minor looseness but the whole thing is efficient and readable.

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?

An output schema and rich annotations cover return shape and safety, so the description need not explain those. What remains missing is the recency/truncation semantics implied by "newest" and the meaning of the default account fallback for a tool whose result set can be large. Adequate but with clear gaps.

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 67%, so two of three parameters are documented in the schema itself (state, account). The description mentions no parameter at all, so it adds nothing about the undocumented `limit` or about how `state` values relate to the live job lifecycle. Baseline 3 is appropriate.

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?

"Newest COM jobs" names the resource and the ordering, and the parenthetical enumerates concrete job kinds (firmware updates, inventory collection, power, OneView sync), so an agent knows what will come back. It also states the payload carries state and result. It stops short of differentiating from any sibling or stating the scope (all accounts vs. one).

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?

No when-to-use guidance: nothing says whether to call this before or instead of the alert/server listing tools, nor when to filter by state. The word "Newest" faintly implies a recency window but the boundary is never stated, leaving the agent to infer behavior.

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