Skip to main content
Glama

TraceVero

Plan an automation task

plan_workflow
Read-onlyIdempotent

Decompose a documented task and find API operations for existing apps. Shows uncovered steps, permission alternatives, costs and untested connector boundaries. Never executes the workflow.

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": "plan_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
appsNo
queryNo
runtimeNoany
task_idNo
evidenceNo
read_onlyNo
granted_scopesNo

Output Schema

NameRequiredDescriptionDefault
taskNo
stepsYes
statusYes
coverageYes
rule_versionYes
catalog_versionYes
dataset_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description still adds real value by enumerating the analysis surface the agent will get back — uncovered steps, permission alternatives, costs, and untested connector boundaries — which is behavioral context not present in the 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?

Three short sentences, front-loaded with the action, then the outputs, then the hard boundary. No filler and nothing buried mid-paragraph.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The purpose and the analysis outputs are well covered, and an output schema exists so return formatting is not the description's job. However, with seven optional parameters at 0% schema coverage and no required fields, an agent gets no guidance on how to compose a call or what a zero-argument invocation yields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 7 parameters, so the description carries the full burden and largely fails it. Only 'task' and 'existing apps' are loosely echoed; nothing explains what 'query', 'runtime', 'evidence', 'read_only', or 'granted_scopes' do or how they change the plan.

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

Purpose4/5

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

The description states a specific verb+resource pair ('Decompose a documented task and find API operations for existing apps') and scopes it to planning rather than execution. It is clearly distinct from execution-oriented tools, though it never explicitly names how it differs from siblings like 'configure' or 'validate_config'.

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

Usage Guidelines3/5

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

Usage is only implied: 'Never executes the workflow' suggests this is the pre-execution planning step, but the description never says when to choose it over 'compare', 'validate_config', or 'configure', nor any precondition such as needing a documented task first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources