Skip to main content
Glama

analyze_workflow

Retrieve detailed analysis of a single workflow: member nodes, inference signals, top-5 risk nodes with breakdown, and adversarial probes. Use after list_workflows to examine the highest-risk workflow.

Instructions

Deep-dive on a single workflow by id: returns every member node, every inference signal that placed it in this workflow (path token / import token / symbol token + weight), the top-5 highest-risk nodes with full risk breakdown, all runtime-risk hypotheses, and the adversarial probe deck. Use this after list_workflows surfaces the one you care about — typically the highest-max-risk workflow affected by a PR.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdYesWorkflow identifier from list_workflows (e.g., 'payments', 'authentication', 'webhooks').

Implementation Reference

  • The WorkflowDomain interface representing the return type for a single workflow's domain data (id, name, kind, members, signals, confidence).
    export interface WorkflowDomain {
        id: string;                  // stable slug (e.g. "authentication")
        name: string;                // pretty label
        kind: WorkflowKind;
        memberNodeIds: string[];
        signals: WorkflowSignal[];   // why we clustered these
        confidence: number;          // 0..100 — strength of inference
    }
Behavior4/5

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

No annotations provided, so the description carries the full burden. It discloses the extensive data returned (nodes, signals, risks, hypotheses, probe deck) but does not explicitly state read-only nature or potential side effects. However, the detailed output list provides strong transparency.

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?

Two sentences: first lists outputs, second gives usage guidance. Front-loaded with purpose, no wasted words. Perfectly concise.

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?

For a complex tool with 1 parameter, no output schema, and no annotations, the description provides a comprehensive list of output components. It lacks output format details but covers the key elements sufficiently.

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 coverage is 100% with a clear description of workflowId. The description adds context by mentioning it comes from list_workflows, but this largely reiterates the schema description. Baseline 3 is appropriate.

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 performs a deep-dive on a single workflow by ID, listing specific components such as member nodes, inference signals, top-5 high-risk nodes, runtime-risk hypotheses, and adversarial probe deck. It distinguishes itself from the sibling 'list_workflows' by indicating it is for detailed analysis of one workflow.

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: after list_workflows surfaces a workflow, typically the highest-max-risk one affected by a PR. This gives clear context and implies list_workflows as the alternative for discovery.

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/vighriday/Veris'

If you have feedback or need assistance with the MCP directory API, please join our Discord server