Skip to main content
Glama

info

Retrieve project structure and workflow details from McFlow to understand organization and automate development processes.

Instructions

Get project or workflow structure information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesProject name

Implementation Reference

  • The handler case in ToolHandler.handleTool that executes the 'info' tool by calling getProjectInfo on the workflow manager.
    case 'info':
      return await this.workflowManager.getProjectInfo(args?.project as string);
  • The input schema and definition for the 'info' tool in the tool registry.
    {
      name: 'info',
      description: 'Get project or workflow structure information',
      inputSchema: {
        type: 'object',
        properties: {
          project: {
            type: 'string',
            description: 'Project name',
          },
        },
        required: ['project'],
      },
    },
  • Registers all tools including 'info' via getToolDefinitions() in the MCP server's listTools handler.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: getToolDefinitions(),
    }));
  • Core helper function implementing the project information logic: detects structure, scans directories for workflows, and formats response.
    async getProjectInfo(project?: string): Promise<any> {
      try {
        if (this.structure.type === 'simple') {
          // Simple structure: return info about the single workflows folder
          const info: any = {
            type: 'simple',
            workflowsPath: 'workflows/',
            workflows: [],
          };
          
          const workflowsDir = this.workflowsPath;  // Already points to workflows folder
          try {
            const files = await fs.readdir(workflowsDir);
            info.workflows = files.filter(f => f.endsWith('.json')).map(f => f.replace('.json', ''));
          } catch {}
          
          // Check for README and .env
          try {
            await fs.access(path.join(this.workflowsPath, 'README.md'));
            info.hasReadme = true;
          } catch {}
          
          try {
            await fs.access(path.join(this.workflowsPath, '.env.example'));
            info.hasEnvExample = true;
          } catch {}
          
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(info, null, 2),
              },
            ],
          };
        } else if (this.structure.type === 'multi-project') {
          if (project) {
            // Get info for specific project
            const projectPath = path.join(this.workflowsPath, project);
            const info: any = {
              name: project,
              type: 'multi-project',
              workflows: [],
            };
            
            const workflowsDir = path.join(projectPath, 'workflows');
            try {
              const files = await fs.readdir(workflowsDir);
              info.workflows = files.filter(f => f.endsWith('.json')).map(f => f.replace('.json', ''));
            } catch {}
            
            return {
              content: [
                {
                  type: 'text',
                  text: JSON.stringify(info, null, 2),
                },
              ],
            };
          } else {
            // List all projects
            return {
              content: [
                {
                  type: 'text',
                  text: JSON.stringify({
                    type: 'multi-project',
                    projects: this.structure.projects || [],
                  }, null, 2),
                },
              ],
            };
          }
        }
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                type: 'unknown',
                message: 'Could not determine project structure',
              }, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new Error(`Failed to get project info: ${error}`);
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a read-only operation ('Get'), but doesn't disclose behavioral traits such as permissions needed, rate limits, or what happens if the project doesn't exist. This is a significant gap 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 a single, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse, though it could be more specific to improve clarity without losing conciseness.

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 no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't explain what 'structure information' entails or the return format, leaving the agent uncertain about the tool's behavior and output. More context is needed for adequate understanding.

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%, with the parameter 'project' documented as 'Project name'. The description adds no additional meaning beyond the schema, such as format examples or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Get project or workflow structure information' states a clear verb ('Get') and resource ('project or workflow structure information'), but it's vague about what specific information is retrieved and doesn't distinguish from sibling tools like 'list', 'status', or 'read'. It provides a basic purpose but lacks specificity.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'list', 'status', and 'read' available, the description doesn't indicate if this is for metadata, configuration, or other structural details, leaving the agent without context for tool selection.

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/mckinleymedia/mcflow-mcp'

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