Skip to main content
Glama

list_job_recipes

Read-only

Lists deterministic workflows that execute without model calls, enabling users to find repeatable local jobs for the FreeRemoteDesktop bridge.

Instructions

List deterministic workflows that make zero model calls

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_job_recipes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety and scope are largely covered. The description does add one genuine behavioral fact beyond the annotations: the listed items are deterministic and make zero model calls, which is a real selection criterion. It still says nothing about result ordering, size, or what fields a listed workflow exposes.

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?

A single short sentence with the key constraint front-loaded and no wasted words. It is slightly under-specified rather than bloated, so conciseness itself is not the problem.

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?

With no output schema and no annotations about return content, the description leaves the agent guessing what a 'recipe' record actually contains and how it connects to run_job or job_history. For a discovery/listing tool, some indication of what is returned and how it is used next is needed.

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?

The tool takes zero parameters, which is the baseline-4 case; the description cannot be faulted for missing parameter meaning. It also correctly implies there are no filtering options, consistent with the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('List') and a resource ('deterministic workflows... that make zero model calls'), so the intent is discernible. However, 'recipes' from the tool name is never defined, and nothing distinguishes this list from siblings like job_history or list_directory, which could plausibly also enumerate workflows.

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?

There is no when-to-use guidance at all. The agent is not told whether to call this before run_job, how it differs from job_history, or whether any prerequisites exist. The only implicit cue is the filter criterion, which hints at a selection condition but never frames it as usage guidance.

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