Skip to main content
Glama
noodlemctwoodle

Sentinel Solutions MCP Server

get_solution_details

Retrieve detailed information about a specific Microsoft Sentinel solution, including data connectors, Log Analytics tables, and security content such as detections and playbooks, by analyzing only the requested solution for quick results.

Instructions

Get detailed information about a specific solution (fast - only analyzes requested solution)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler definition with name 'get_solution_details', input schema (solution_name), and execute function that delegates to SingleSolutionLoader.analyzeSolution().
    export const getSolutionDetailsTool = {
      name: 'get_solution_details',
      description: 'Get detailed information about a specific solution (fast - only analyzes requested solution)',
      inputSchema: z.object({
        solution_name: z.string().describe('The solution name'),
      }),
      execute: async (args: { solution_name: string }): Promise<SolutionDetails | null> => {
        // Use optimized single-solution analyzer - no need to analyze all 480!
        const github = repoManager.getGitHubClient();
        const analyzer = new SingleSolutionLoader(github);
    
        return await analyzer.analyzeSolution(args.solution_name);
      },
    };
  • The core handler logic that loads solution metadata, fetches connector files, resolves parsers, and returns detailed solution info including connectors and unique tables.
    async analyzeSolution(solutionName: string): Promise<SolutionDetails | null> {
      console.error(`Analyzing solution: ${solutionName}`);
    
      const solutionPath = `Solutions/${solutionName}`;
    
      // 1. Load metadata
      const metadata = await this.loadSolutionMetadata(solutionPath, solutionName);
      if (!metadata) {
        return null;
      }
    
      // 2. Get tree to find connector and parser files
      console.error('Fetching solution files from GitHub...');
      const tree = await this.github.getTree();
    
      // 3. Find connector files for this solution only
      const connectorFiles = tree.tree.filter(
        (item) =>
          item.path.startsWith(`${solutionPath}/Data Connectors`) &&
          (item.path.endsWith('.json') || item.path.endsWith('.JSON')) &&
          item.type === 'blob'
      );
    
      console.error(`Found ${connectorFiles.length} connectors`);
    
      if (connectorFiles.length === 0) {
        return {
          metadata,
          connectors: [],
          uniqueTables: [],
          githubUrl: this.github.getGitHubUrl(solutionPath),
        };
      }
    
      // 4. Load parsers for this solution
      const parserResolver = new ParserResolver(solutionPath, tree.tree, this.github);
      await parserResolver.loadParsers();
    
      // 5. Analyze connectors
      const connectors: Array<{
        id: string;
        title: string;
        description?: string;
        tables: string[];
      }> = [];
    
      const allTables = new Set<string>();
    
      for (const connectorFile of connectorFiles) {
        const connectorData = await this.analyzeConnector(
          connectorFile.path,
          parserResolver
        );
    
        if (connectorData) {
          connectors.push(connectorData);
          connectorData.tables.forEach((table) => allTables.add(table));
        }
      }
    
      console.error(`Analysis complete! Found ${allTables.size} unique tables`);
    
      return {
        metadata,
        connectors,
        uniqueTables: Array.from(allTables),
        githubUrl: this.github.getGitHubUrl(solutionPath),
      };
    }
  • The SolutionDetails type definition - the return type of get_solution_details tool.
    export interface SolutionDetails {
      metadata: SolutionMetadata;
      connectors: Array<{
        id: string;
        title: string;
        description?: string;
        tables: string[];
      }>;
      uniqueTables: string[];
      githubUrl?: string;
    }
  • The input schema for the tool, requiring a 'solution_name' string parameter.
    inputSchema: z.object({
      solution_name: z.string().describe('The solution name'),
    }),
  • Tool re-exported in the consolidated index.ts, making it available as part of the allTools collection.
    getSolutionDetailsTool,
Behavior3/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 adds behavioral context ('fast', 'only analyzes requested') beyond the name, but does not disclose return format, read-only nature, or potential side effects. Adequate but not thorough.

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 sentence of 12 words, front-loading the purpose. It is concise and clear, though could benefit from structured enumeration of return fields or usage hints.

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?

Given low complexity (one parameter, no output schema, no annotations), the description is minimally complete. It states purpose and a key behavioral trait (speed) but lacks details on return shape, errors, permissions, or when to prefer siblings.

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 schema has one parameter (solution_name) with 100% coverage. The description does not add meaning beyond what the schema provides (e.g., valid values or format). Baseline 3 is appropriate as schema covers the parameter fully.

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 the tool gets detailed information about a specific solution, using a specific verb and resource. It distinguishes from sibling tools like list_solutions or analyze_solutions by emphasizing speed and targeted analysis.

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

Usage Guidelines3/5

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

The description implies use for a single solution (via 'only analyzes requested solution') but does not explicitly state when to use this versus alternatives like search_solutions or analyze_solutions. No exclusions or contextual cues are provided.

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/noodlemctwoodle/sentinel-solutions-mcp'

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