slurm_get_jobRetrieve detailed status and accounting data for a specific Slurm job by job ID to monitor progress, diagnose failures, and review resource usage.
Inspect one registered job using the queue and accounting records.
| Name | Required | Description | Default |
|---|---|---|---|
| job_id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so the description carries the full burden. It helpfully discloses that data comes from both queue and accounting records (implying running and historical jobs), but says nothing about permissions, behavior for unknown job_ids, or whether job_id must be live or completed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no waste. It is efficient, though the brevity is partly why other dimensions are underserved.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema and no annotations, so the description should do more. It does hint at the return sources (queue and accounting records), which is genuinely useful, but it omits identifier format and error/precondition behavior needed to call the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for the single job_id param, so the description must compensate and does not: it never states the identifier format (numeric Slurm ID vs. name/string) or whether it must reference a currently active job. Only the implied 'one job' scope gives any meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Inspect') and resource ('one registered job'), which cleanly distinguishes it from the list-oriented siblings like slurm_list_jobs and slurm_watch_job. 'Registered job' is slightly vague about whether registration is a distinct state, but the intent is clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to call this versus slurm_list_jobs, slurm_watch_job, or slurm_read_log. The agent must infer from the name alone that this is the single-job detail lookup, with no stated preconditions or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.