Skip to main content
Glama
NGS360

NGS360 MCP Server

Official
by NGS360

submit_job

Submit a batch job to AWS Batch by specifying job name, definition, queue, command, and user. Optionally include environment variables.

Instructions

Submit a new batch job to AWS Batch.

Args: job_name: Name for the batch job job_definition: AWS Batch job definition ARN job_queue: AWS Batch job queue name command: Command string to execute user: Username submitting the job environment: Optional list of environment variables [{"name": "KEY", "value": "VAL"}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYes
commandYes
job_nameYes
job_queueYes
environmentNo
job_definitionYes
Behavior2/5

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

No annotations provided, so description must carry full burden. It does not disclose whether submission is synchronous, what happens on failure, return value, or any quotas/limits. Minimal behavioral info.

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?

The description is concise, front-loaded with purpose, and the Args block is clearly structured. No superfluous text.

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 or annotations, the description should cover return value (e.g., job ID), asynchronous behavior, and permissions. It lacks these, leaving gaps for an AI agent.

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

Parameters4/5

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

Input schema has 0% description coverage, but the description's Args block adds meaningful explanations for all 6 parameters (e.g., 'command: Command string to execute'). This compensates well, though more detail (e.g., accepted formats) could help.

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 verb 'Submit' and resource 'new batch job to AWS Batch', which is specific and distinguishes from sibling tools like submit_demux_job and submit_pipeline_job.

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 guidance on when to use this tool versus alternatives (e.g., submit_demux_job) or prerequisites. The description only states the function without context.

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/NGS360/mcp-server'

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