Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

List Environment Jobs

list_environment_jobs
Read-onlyIdempotent

Retrieve jobs currently deployed to a Coalesce environment to view what the scheduler will execute, separate from in-progress workspace edits.

Instructions

List all jobs deployed to a Coalesce environment. Jobs define which nodes run together — pair this with list_environment_nodes when planning a refresh, or with create_workspace_job when authoring new schedules.

Different from listing workspace-side jobs: this returns the jobs currently deployed to the target environment (what the scheduler will execute), not the in-flight workspace edits that may not be deployed yet.

Args:

  • environmentID (string, required): The environment ID

  • limit, startingFrom, orderBy, orderByDirection: Pagination

Returns: { data: Job[], next?: string, total?: number }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return (max 500)
orderByNoField to sort by (required with startingFrom)
startingFromNoCursor from previous response's next field
environmentIDYesThe environment ID
orderByDirectionNoSort direction

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
nextNo
totalNo
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false. The description adds behavioral context about the tool reading deployed jobs vs workspace edits, and describes the return format. This adds value beyond the annotations, though not extensively.

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 and well-structured: first sentence states purpose, then usage guidance, then differentiation, then parameter/return summary. Every sentence adds value with no repetition or filler.

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?

The description is complete for a simple list tool: explains purpose, usage context, differentiation, and return format. Output schema exists (description mentions Job[]). While it omits error conditions, annotations cover safety. The description is sufficient.

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 baseline is 3. The description mentions arguments and their purpose (pagination), but this information is already present in the schema descriptions. No significant additional meaning beyond schema.

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 explicitly states 'List all jobs deployed to a Coalesce environment' with a specific verb and resource. It distinguishes from sibling tools like list_environment_nodes and create_workspace_job, and clarifies the difference from workspace-side jobs.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use the tool: pair with list_environment_nodes for refresh planning or with create_workspace_job for authoring schedules. It also clarifies that it returns deployed jobs, not in-flight workspace edits, which helps avoid misuse.

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/Coalesce-Software-Inc/coalesce-transform-mcp'

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