Skip to main content
Glama

get_flow

Retrieve detailed workflow information by its ID, including steps, descriptions, and input schemas, for executing sequences in VeyraX MCP server.

Instructions

"Use this tool to retrieve a specific workflow by its ID.

Workflow is sequence of steps that are executed in order to get some result. Flow comes with description, steps and input schema of all methods to call.

You can call this tool once you have a flowId which usually you can get from: user directly OR using get-tools method."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flowIdYesThe ID of the workflow to retrieve.

Implementation Reference

  • The execute method implements the core logic of the 'get_flow' tool, fetching workflow data by ID from the API and returning it as JSON.
    async execute({ flowId }: z.infer<typeof this.schema>) {
      try {
        const { data } = await veyraxClient.get(`/flow/get-flow/${flowId}`);
    
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify(data, null, 2),
            },
          ],
        };
      } catch (error) {
        throw error;
      }
    }
  • Zod schema defining the input for the tool: a required flowId string.
    schema = z.object({
      flowId: z.string().describe("The ID of the workflow to retrieve."),
    });
  • src/index.ts:15-15 (registration)
    Registers the GetFlowTool instance with the MCP server.
    new GetFlowTool().register(server);
Behavior2/5

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

With no annotations provided, the description carries full burden of behavioral disclosure. It states this is a retrieval operation but doesn't mention whether it requires authentication, has rate limits, what happens with invalid IDs, or what the return format looks like. The description adds some context about what a workflow contains, but lacks critical behavioral details for a tool with no annotation coverage.

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?

The description is appropriately sized with three sentences. The first sentence clearly states the purpose, the second provides helpful context about workflows, and the third gives usage guidance. Each sentence earns its place, though the second sentence could be slightly more concise.

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?

For a single-parameter retrieval tool with no output schema and no annotations, the description provides adequate basic information but lacks details about return values, error conditions, and behavioral constraints. It covers the core purpose and usage but doesn't fully compensate for the missing structured information.

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 the single 'flowId' parameter. The description adds minimal value beyond the schema by mentioning that flow IDs can come from 'user directly OR using get-tools method', but doesn't provide format examples or validation rules. This meets the baseline for high schema coverage.

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 clearly states the tool's purpose: 'retrieve a specific workflow by its ID' with additional context about what a workflow is. It distinguishes from sibling 'get_tools' by focusing on retrieving a single workflow rather than listing tools. However, it doesn't explicitly differentiate from 'tool_call' which might execute workflows.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool: 'once you have a flowId' and mentions 'get-tools method' as an alternative way to obtain flow IDs. It doesn't explicitly state when NOT to use it or provide detailed alternatives, but the guidance is sufficient for basic usage.

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

Related 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/VeyraX/veyrax-mcp'

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