Skip to main content
Glama

Meta Council

by com.meta-council
OverviewDiscussionsAdmin

Test Workflow Step

test_workflow_step

Run exactly ONE step of a workflow and return what it produced, so you can iterate on a single step's wording without running the steps before it. THIS SPENDS CREDITS EXACTLY LIKE A REAL STEP: the step runs on a real model through the same engine a full run uses and is billed identically -- it is not a simulation, a dry run, or a free preview. If you want to check a workflow's shape, parameters, models and cost estimate for free, use plan_workflow instead; that one runs nothing. Starts no session, so there is nothing to poll and nothing to advance. Requires authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoThe input the step works on, exactly as you would pass it to run_workflow. Optional -- omit for a step whose instruction already carries everything it needs.
workflowYesThe workflow slug (from list_workflows), e.g. 'due_diligence'.
parametersNoOptional values for the workflow's declared parameters, as a flat name-to-value object, e.g. {"region": "EU"}. They are substituted into the step wording the same way a real run substitutes them.
step_indexYesWhich step to run, counting from 0. A workflow with 4 steps accepts 0 to 3; anything else is refused without spending.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "text": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "text"
-  ],
-  "type": "object"
-}New value: +null
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations cover safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds high-value behavior beyond them: it bills credits exactly like a real run, is not a dry run or free preview, starts no session so there is nothing to poll or advance, and requires authentication. No contradiction with annotations.

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?

Front-loaded with the core behavior and alternatives, and every sentence carries information. The billing warning is slightly repetitive ('not a simulation, a dry run, or a free preview'), which costs a point but the emphasis is defensible for a credit-spending tool.

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?

Covers cost, auth, and session/state behavior thoroughly, which is what an agent most needs to avoid accidental spend. The only gap is that with no output schema, the shape of 'what it produced' is not described beyond that phrase.

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 description coverage is 100%, so the schema already documents all four parameters including step_index bounds and parameter substitution semantics. The description adds only marginal param context ('exactly as you would pass it to run_workflow'), so baseline 3 applies.

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?

States a specific verb and resource ('Run exactly ONE step of a workflow and return what it produced') plus the intent (iterate on a single step's wording without running prior steps). This clearly separates it from run_workflow and plan_workflow without needing either schema.

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 names the alternative for a different need ('if you want to check a workflow's shape, parameters, models and cost estimate for free, use plan_workflow instead'), and gives a clear when-to-use (isolate a single step). Exclusions are stated, not implied.

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

All Meta Council toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources