Skip to main content
Glama

get_findings_json

Execute GauntletCI on a .NET repository and retrieve behavioral change risk findings in raw JSON format for programmatic analysis and integration.

Instructions

Run GauntletCI and return the raw JSON result for programmatic processing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workingDirectoryYesAbsolute path to the .NET repository root.
sensitivityNobalanced

Implementation Reference

  • src/index.ts:106-125 (registration)
    The 'get_findings_json' tool is registered in the ListToolsRequestSchema handler with its name, description, and inputSchema (workingDirectory and sensitivity).
    {
      name: "get_findings_json",
      description:
        "Run GauntletCI and return the raw JSON result for programmatic processing.",
      inputSchema: {
        type: "object",
        properties: {
          workingDirectory: {
            type: "string",
            description: "Absolute path to the .NET repository root.",
          },
          sensitivity: {
            type: "string",
            enum: ["strict", "balanced", "permissive"],
            default: "balanced",
          },
        },
        required: ["workingDirectory"],
      },
    },
  • Input schema for get_findings_json: object with workingDirectory (string, required) and sensitivity (enum: strict/balanced/permissive, default: balanced).
      inputSchema: {
        type: "object",
        properties: {
          workingDirectory: {
            type: "string",
            description: "Absolute path to the .NET repository root.",
          },
          sensitivity: {
            type: "string",
            enum: ["strict", "balanced", "permissive"],
            default: "balanced",
          },
        },
        required: ["workingDirectory"],
      },
    },
  • Handler logic for 'get_findings_json': calls runGauntletCI with 'json' format, checks exit code (0 or 1 allowed), returns raw JSON output as text.
    if (name === "get_findings_json") {
      const { output, exitCode } = runGauntletCI(workingDirectory, sensitivity, "json");
      if (exitCode !== 0 && exitCode !== 1) {
        return {
          content: [{ type: "text", text: `GauntletCI error (exit ${exitCode}): ${output}` }],
          isError: true,
        };
      }
      return { content: [{ type: "text", text: output }] };
    }
  • The runGauntletCI helper function that spawns the 'gauntletci analyze' CLI process with the given working directory, sensitivity, and output format. Used by get_findings_json handler with format='json'.
    export function runGauntletCI(
      workingDir: string,
      sensitivity: string,
      outputFormat: "json" | "sarif" | "text"
    ): { output: string; exitCode: number } {
      const result = spawnSync(
        "gauntletci",
        ["analyze", "--output", outputFormat, "--no-banner", "--sensitivity", sensitivity, "--no-llm"],
        {
          cwd: workingDir,
          encoding: "utf8",
          shell: process.platform === "win32",
        }
      );
    
      return {
        output: result.stdout ?? "",
        exitCode: result.status ?? -1,
      };
    }
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It states 'Run GauntletCI' but does not mention side effects, required permissions, rate limits, or that it may execute external commands.

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?

Single sentence of 11 words is concise. However, it lacks detail, bordering on under-specification. Front-loaded with action, but could be more informative.

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 output schema and two parameters, the description should explain return format, installation requirements, or usage context. It only states 'raw JSON result' without specifics, making it incomplete for programmatic use.

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

Parameters2/5

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

Schema coverage is 50%; description adds no further parameter meaning. The workingDirectory is adequately described in schema, but sensitivity enum values are not explained. Description repeats minimal info.

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

Purpose5/5

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

The description clearly states that the tool runs GauntletCI and returns raw JSON for programmatic processing. The sibling tools analyze_commit and get_sarif imply different purposes, providing implicit differentiation.

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 on when to use this tool versus alternatives. No mention of prerequisites, when not to use, or which scenarios are appropriate.

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/EricCogen/GauntletCI-MCP'

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