Skip to main content
Glama
Sign In
coalesce-transform-mcp

coalesce-transform-mcp

Official
by Coalesce-Software-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create Workspace Job

create_workspace_job

Create a job in a Coalesce workspace to specify nodes to run together using include and exclude selectors.

Instructions

Create a new job in a Coalesce workspace. Jobs define which nodes to run together.

Args:

  • workspaceID (string, required): The workspace ID

  • name (string, required): Job name

  • includeSelector (string, required): Node selector. Format: '{ location: LOC name: NAME } OR { location: LOC name: NAME }'. Use empty string to include nothing

  • excludeSelector (string, required): Node exclusion selector. Same format as includeSelector. Use empty string to exclude nothing

Returns: Created job with assigned ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspaceID": "<workspaceID>",
      "name": "<name>",
      "includeSelector": "<includeSelector>",
      "excludeSelector": "<excludeSelector>"
    },
    "name": "create_workspace_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName for the job
workspaceIDYesThe workspace ID
excludeSelectorYesNode exclusion selector string. Same format as includeSelector. Use empty string to exclude nothing.
includeSelectorYesNode selector string. Format: '{ location: LOC name: NAME } OR { location: LOC name: NAME }'. Use empty string to include nothing.

Output Schema

NameRequiredDescriptionDefault
idNo
nameNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=false (write operation) and destructiveHint=false. The description adds value by detailing the required parameters and the format of selectors, and noting that empty strings exclude nothing. This provides transparency beyond annotations.

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 extremely concise—three short paragraphs covering purpose, parameters with examples, and return value. Every sentence adds value with no redundancy.

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?

Given the complexity (4 required params, all simple strings) and the presence of an output schema (though not shown), the description is complete enough. It covers all necessary aspects for a creation tool: what it does, required inputs with format, and the return value.

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?

Schema coverage is 100%, but the description enhances understanding by providing concrete format examples for includeSelector and excludeSelector, and clarifying that empty strings are valid. This adds meaning beyond the schema's generic descriptions.

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 it creates a new job in a Coalesce workspace, using the specific verb 'Create', and identifies the resource type. It distinguishes from sibling tools like update_workspace_job, delete_workspace_job, and find_jobs_by_name by focusing on creation.

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?

The description specifies what the tool does and provides detailed parameter information, making it clear when to use it (to create a job). It does not explicitly state when not to use it or list alternatives, but given its unique purpose among siblings, the context is sufficient.

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

Deploy Server

Other Tools