Skip to main content
Glama
0xjcf
by 0xjcf

analyze-files

Analyze code files to detect syntax issues, visualize dependencies, and support development workflows through comprehensive code analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesYesFiles to analyze

Implementation Reference

  • Handler function that processes an array of files, calculates metrics for each using calculateMetrics helper, and returns a JSON-formatted text response with results.
    async (args: { files: Array<{ path: string; content: string }> }) => {
      const { files } = args;
      
      // Analyze each file
      const results = await Promise.all(
        files.map(async (file: { path: string; content: string }) => {
          const extension = path.extname(file.path).slice(1);
          const metrics = calculateMetrics(file.content, extension);
          
          return {
            file: path.basename(file.path),
            metrics
          };
        })
      );
      
      return {
        content: [{
          type: "text",
          text: JSON.stringify({ results }, null, 2)
        }]
      };
    }
  • Zod input schema defining the expected arguments: an array of objects each containing file path and content.
    {
      files: z.array(z.object({
        path: z.string().describe("Path to the file"),
        content: z.string().describe("Content of the file")
      })).describe("Files to analyze")
  • MCP server tool registration for 'analyze-files', specifying input schema and handler function within registerIdeTools.
    server.tool(
      "analyze-files",
      {
        files: z.array(z.object({
          path: z.string().describe("Path to the file"),
          content: z.string().describe("Content of the file")
        })).describe("Files to analyze")
      },
      async (args: { files: Array<{ path: string; content: string }> }) => {
        const { files } = args;
        
        // Analyze each file
        const results = await Promise.all(
          files.map(async (file: { path: string; content: string }) => {
            const extension = path.extname(file.path).slice(1);
            const metrics = calculateMetrics(file.content, extension);
            
            return {
              file: path.basename(file.path),
              metrics
            };
          })
        );
        
        return {
          content: [{
            type: "text",
            text: JSON.stringify({ results }, null, 2)
          }]
        };
      }
    );
  • Supporting function called by the analyze-files handler to compute basic metrics (lines of code, complexity score, maintainability rating) for each file.
    function calculateMetrics(
      content: string, 
      language: string
    ): {
      linesOfCode: number;
      complexity: number;
      maintainability: string;
    } {
      // This is a placeholder implementation
      // In a real implementation, you would calculate actual metrics
      
      const lines = content.split("\n");
      
      return {
        linesOfCode: lines.length,
        complexity: Math.floor(lines.length / 10) + 1,
        maintainability: "medium"
      };
    } 
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/0xjcf/MCP_CodeAnalysis'

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