Skip to main content
Glama

hpc_submit_chain

Submit a chain of dependent jobs that checkpoint and resume to run workloads beyond the 24-hour GPU walltime limit on the DTU HPC cluster.

Instructions

Submit a checkpoint-resume chain of dependent jobs for runs longer than the 24h GPU walltime cap. The training command must support --resume-from and checkpoint on SIGUSR2 -- verify this BEFORE submitting.

Args: profile_path: Path to the local profile YAML. run_id: Short identifier; segments become .0, .1, ... project_dir: Local project directory for manifests. segments: Number of walltime-sized segments (total = segments x walltime). resource_overrides: Optional JSON object overriding profile resources. confirmed_by_user: Set ONLY after explicit human approval when above the profile's confirmation thresholds. Chains are always above the 12h default threshold in total, so this usually requires asking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idYes
segmentsYes
project_dirYes
profile_pathYes
confirmed_by_userNo
resource_overridesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Describes chain submission and dependency; mentions confirmation thresholds. No annotations, so description carries burden. Lacks failure behavior details.

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

Conciseness5/5

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

Efficient front-loaded paragraph explaining purpose and prerequisite, followed by bullet list of args. No redundant sentences.

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

Completeness5/5

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

Covers purpose, prerequisites, parameter details, and confirmation need. Output schema exists for return values, so completeness is high.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaning to all 6 parameters: naming convention for segments, required human approval for confirmed_by_user, optional JSON for resource_overrides. 0% schema coverage compensated fully.

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?

Clear verb 'submit' and specific resource 'checkpoint-resume chain of dependent jobs' for runs >24h. Distinct from siblings like hpc_submit_run.

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

Usage Guidelines4/5

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

Explicit prerequisite: training command must support --resume-from and SIGUSR2. Implicit context for long runs, but no direct comparison to alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PV-Bhat/dtu-hpc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server