Skip to main content
Glama
folderr-tech

Folderr

Official
by folderr-tech

get_workflow_inputs

Retrieve required input parameters for a Folderr workflow to prepare for execution.

Instructions

Get the required inputs for a workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYesID of the workflow

Implementation Reference

  • The handler function that executes the tool logic: authenticates, calls the Folderr API to get workflow inputs for the given workflow_id, and returns the JSON response or an error message.
    private async handleGetWorkflowInputs(args: any) {
      if (!this.config.token) {
        throw new McpError(ErrorCode.InvalidRequest, 'Not logged in');
      }
    
      try {
        const response = await this.axiosInstance.get(`/api/workflows/api-client/${args.workflow_id}/inputs`);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: 'text',
              text: `Failed to get workflow inputs: ${error.response?.data?.message || error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema defining the required 'workflow_id' parameter for the tool.
    inputSchema: {
      type: 'object',
      properties: {
        workflow_id: {
          type: 'string',
          description: 'ID of the workflow',
        },
      },
      required: ['workflow_id'],
    },
  • src/index.ts:179-192 (registration)
    Tool registration in the ListTools response, defining name, description, and input schema.
    {
      name: 'get_workflow_inputs',
      description: 'Get the required inputs for a workflow',
      inputSchema: {
        type: 'object',
        properties: {
          workflow_id: {
            type: 'string',
            description: 'ID of the workflow',
          },
        },
        required: ['workflow_id'],
      },
    },
  • src/index.ts:227-228 (registration)
    Dispatcher case in CallToolRequest handler that routes to the specific handler function.
    case 'get_workflow_inputs':
      return await this.handleGetWorkflowInputs(request.params.arguments);
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states a read operation ('Get'), implying non-destructive behavior, but does not disclose other traits such as authentication needs, rate limits, error conditions, or what the return format looks like (no output schema). This leaves significant gaps 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no wasted words. It is front-loaded with the core purpose and appropriately sized for a simple tool, making it efficient and easy to parse.

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?

Given the lack of annotations and output schema, the description is incomplete. It does not explain what 'required inputs' entails (e.g., structure, types, defaults) or behavioral aspects like error handling. For a tool that retrieves configuration data, more context is needed to guide effective use.

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?

The input schema has 100% description coverage, with the single parameter 'workflow_id' documented as 'ID of the workflow'. The description adds no additional meaning beyond this, such as format examples or sourcing instructions. With high schema coverage, the baseline score of 3 is appropriate.

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 action ('Get') and target ('required inputs for a workflow'), making the purpose understandable. It distinguishes itself from siblings like 'execute_workflow' (which runs workflows) and 'list_workflows' (which lists workflows), but does not explicitly differentiate from other input-related tools (none exist in the sibling list).

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing a workflow ID from 'list_workflows'), exclusions, or contextual cues for selection among siblings like 'ask_assistant' or 'execute_workflow'.

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/folderr-tech/folderr-mcp-server'

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