Skip to main content
Glama
folderr-tech

Folderr

Official
by folderr-tech

list_workflows

Retrieve all available workflows from Folderr to manage and communicate with Assistants through the API.

Instructions

List all available workflows

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_workflows' tool. It checks for authentication, makes a GET request to '/api/workflows', and returns the JSON response as text content, or an error message if failed.
    private async handleListWorkflows() {
      if (!this.config.token) {
        throw new McpError(ErrorCode.InvalidRequest, 'Not logged in');
      }
    
      try {
        const response = await this.axiosInstance.get('/api/workflows');
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: 'text',
              text: `Failed to list workflows: ${error.response?.data?.message || error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • src/index.ts:170-178 (registration)
    Tool registration in the ListTools response, including name, description, and empty input schema (no parameters required).
    {
      name: 'list_workflows',
      description: 'List all available workflows',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • src/index.ts:225-226 (registration)
    Dispatch case in the CallToolRequest handler that routes 'list_workflows' calls to the handleListWorkflows method.
    case 'list_workflows':
      return await this.handleListWorkflows();
  • Input schema for the 'list_workflows' tool, defining no required properties.
    inputSchema: {
      type: 'object',
      properties: {},
      required: [],
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('List') but doesn't describe what 'list' entails—whether it returns summaries or full details, if there's pagination, rate limits, or authentication requirements. This is a significant gap for a tool with zero 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, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 zero-parameter list tool with no output schema, the description is minimally adequate. It states what the tool does but lacks behavioral context (e.g., return format, pagination) and usage guidance relative to siblings. Without annotations, this leaves gaps in understanding how to effectively use the tool.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but it could have mentioned implicit filtering or sorting options. Baseline is 4 for zero-parameter tools.

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 verb ('List') and resource ('workflows') with scope ('all available'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_assistants' or 'get_workflow_inputs', which prevents a perfect score.

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 like 'get_workflow_inputs' or 'execute_workflow'. There's no mention of prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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