Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

Find Environment Jobs by Name

find_jobs_by_name
Read-onlyIdempotent

Find jobs by name in an environment using fuzzy matching, and retrieve each job's ID and recent run history.

Instructions

Fuzzy-match jobs in an environment by name (case-insensitive substring), and return each match with its most recent runs. Use this when the user references a job by name and you need the job's ID or recent execution history.

Scans the last 50 runs in the environment and groups them by matched job. Runs that fall outside that window are not returned — for older history call list_runs with explicit pagination.

Args:

  • environmentID (string, required): The environment ID

  • jobName (string, required): Substring to match (case-insensitive)

  • runLimitPerJob (integer, optional): Max recent runs per matched job (default 5)

Returns: { matches: [{ job: {id, name, includeSelector, excludeSelector}, recentRuns: [{runID, runCounter, runStatus, runType, runStartTime, runEndTime}] }], summary: { jobsMatched, totalRunsReturned, runScanLimit } }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobNameYesSubstring to match against job names (case-insensitive)
environmentIDYesThe environment ID
runLimitPerJobNoMax recent runs per matched job (default 5, max 50)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already declare readOnlyHint=true, etc. The description adds the crucial detail that only the last 50 runs are scanned, runs outside that window are not returned. This explains the behavioral limitation beyond what annotations provide.

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

Conciseness4/5

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

Well-structured: clear purpose, usage context, limitation, then organized Args and Returns blocks. Front-loaded with key information. Every sentence adds value, though the Args block slightly overlaps with the schema.

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?

Given the schema coverage, annotations, and the provided output schema in the description, the description fully explains the tool's behavior, parameters, return format, and limitations. No gaps in understanding for an agent.

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 covers all 3 parameters with descriptions (100% coverage). The description adds the default value of 5 for runLimitPerJob and its maximum of 50, providing marginal additional value. No further semantic enrichment needed.

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 specifies the action: fuzzy-matching jobs by name case-insensitively, returning matches with recent runs. It clearly distinguishes from sibling tools like list_environment_jobs and list_runs by focusing on name-based search with limited run history.

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?

Explicitly states when to use: when the user references a job by name and needs ID or recent execution history. Provides exclusions: runs outside the last 50 are not returned, directing to list_runs with pagination for older history. Names an alternative tool.

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