Skip to main content
Glama
noodlemctwoodle

Sentinel Solutions MCP Server

get_connector_tables

Retrieve Log Analytics table mappings for any Microsoft Sentinel data connector. Provide a connector ID to get the specific tables it sends data to.

Instructions

Get table mappings for a specific connector ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler/execute function for the 'get_connector_tables' tool. It filters cached analysis results by connector_id and returns the matching connector's tables (tableName and detectionMethod).
    export const getConnectorTablesTool = {
      name: 'get_connector_tables',
      description: 'Get table mappings for a specific connector ID',
      inputSchema: z.object({
        connector_id: z.string().describe('The connector ID to look up'),
      }),
      execute: async (args: { connector_id: string }): Promise<ConnectorTables | null> => {
        await ensureAnalysis();
    
        if (!cachedAnalysisResult) {
          throw new Error('Analysis results not available');
        }
    
        const connectorMappings = cachedAnalysisResult.mappings.filter(
          (m) => m.connectorId === args.connector_id
        );
    
        if (connectorMappings.length === 0) {
          return null;
        }
    
        const tables = connectorMappings.map((m) => ({
          tableName: m.tableName,
          detectionMethod: m.detectionMethod || 'unknown',
        }));
    
        return {
          connectorId: args.connector_id,
          connectorTitle: connectorMappings[0].connectorTitle,
          tables,
        };
      },
    };
  • Input schema for the tool, requiring a 'connector_id' string parameter validated via Zod.
    inputSchema: z.object({
      connector_id: z.string().describe('The connector ID to look up'),
    }),
  • The ConnectorTables interface defining the return type: connectorId, connectorTitle, and an array of tables with tableName and detectionMethod.
    export interface ConnectorTables {
      connectorId: string;
      connectorTitle: string;
      tables: Array<{
        tableName: string;
        detectionMethod: string;
      }>;
    }
  • Registration of the tool in the solutionTools array, alongside other tools (analyzeSolutionsTool, searchSolutionsTool, etc.).
    export const solutionTools = [
      analyzeSolutionsTool,
      getConnectorTablesTool,
      searchSolutionsTool,
      getSolutionDetailsTool,
      listTablesTool,
      validateConnectorTool,
    ];
  • Import and re-export of getConnectorTablesTool from solutionTools, making it available as part of the consolidated MCP tools module.
    import {
      analyzeSolutionsTool,
      getConnectorTablesTool,
      searchSolutionsTool,
      getSolutionDetailsTool,
      listTablesTool,
      validateConnectorTool,
      solutionTools,
    } from './solutionTools.js';
Behavior2/5

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

No annotations provided, so description carries full burden. It only states the basic action without mentioning side effects, permissions, caching, or rate limits, which is minimal disclosure for a read operation.

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 with no fluff. Efficient but could be slightly improved by front-loading the key action and resource.

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?

Adequate for a simple one-parameter tool with no output schema, but lacks information about what the table mappings contain or return format.

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?

Input schema has 100% coverage with one parameter. Description adds that it is 'for a specific connector ID', but adds no additional meaning beyond the schema.

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 action 'Get', resource 'table mappings', and scope 'for a specific connector ID', distinguishing it from sibling tools like list_tables or list_data_connectors.

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?

No explicit guidance on when to use or when not to use this tool. The description implies usage when needing table mappings for a connector, but lacks exclusions or alternatives compared to siblings.

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