Skip to main content
Glama

cortex_get_analyzer

Fetch comprehensive details for a given analyzer ID, including its configuration and metadata.

Instructions

Get details about a specific analyzer by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
analyzerIdYesThe analyzer ID

Implementation Reference

  • The tool handler for cortex_get_analyzer – takes an analyzerId param, calls client.getAnalyzer(), and returns the analyzer details as JSON.
    server.tool(
      "cortex_get_analyzer",
      "Get details about a specific analyzer by ID",
      {
        analyzerId: z.string().describe("The analyzer ID"),
      },
      async ({ analyzerId }) => {
        try {
          const analyzer = await client.getAnalyzer(analyzerId);
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify(analyzer, null, 2),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text" as const,
                text: `Error getting analyzer: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
            isError: true,
          };
        }
      },
  • Input schema for cortex_get_analyzer defines a single required 'analyzerId' string parameter.
    {
      analyzerId: z.string().describe("The analyzer ID"),
  • Tool registration via server.tool('cortex_get_analyzer', ...) inside registerAnalyzerTools() which is called from src/index.ts line 34.
    server.tool(
      "cortex_get_analyzer",
      "Get details about a specific analyzer by ID",
      {
        analyzerId: z.string().describe("The analyzer ID"),
      },
      async ({ analyzerId }) => {
        try {
          const analyzer = await client.getAnalyzer(analyzerId);
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify(analyzer, null, 2),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text" as const,
                text: `Error getting analyzer: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
            isError: true,
          };
        }
      },
    );
  • Client helper that performs GET /api/analyzer/{analyzerId} to fetch the analyzer from Cortex API.
    async getAnalyzer(analyzerId: string): Promise<Analyzer> {
      return this.request<Analyzer>(`/analyzer/${encodeURIComponent(analyzerId)}`);
  • The Analyzer interface type definition returned by getAnalyzer.
    export interface Analyzer {
      id: string;
      name: string;
      version: string;
      description: string;
      dataTypeList: string[];
      cortexIds?: string[];
      rate?: number;
      rateUnit?: string;
      maxTlp?: number;
      maxPap?: number;
      createdBy?: string;
      createdAt?: number;
      updatedBy?: string;
      updatedAt?: number;
      workerDefinitionId?: string;
      configuration?: Record<string, unknown>;
      baseConfig?: string;
      dockerImage?: string;
      jobCache?: number;
      type?: string;
    }
Behavior2/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 only says 'get details', implying a read operation, but does not disclose any behavioral traits such as required permissions, rate limits, error handling (e.g., if analyzer ID not found), or whether it returns full or partial details. This is insufficient for an agent to anticipate side effects or restrictions.

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, very concise. It efficiently conveys the core purpose without fluff. However, it could benefit from a bit more detail without becoming verbose.

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 the simplicity of the tool (1 required param, no output schema), the description is incomplete. It does not specify what 'details' are returned (e.g., configuration, status) or any potential error conditions. An agent would need to rely on external knowledge or trial and error.

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 input schema has 100% coverage with a description for analyzerId. The tool description adds no extra meaning beyond 'by ID'. Baseline 3 is appropriate since the schema already documents the parameter adequately.

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 it retrieves details about a specific analyzer by ID. The verb 'get' and 'details' make the purpose unambiguous, and it distinguishes from sibling tools like cortex_list_analyzers (list) or cortex_run_analyzer (action).

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 vs alternatives like cortex_list_analyzer_definitions or cortex_get_job. The description does not mention prerequisites, limitations, or when not to use it. Since there are many sibling tools, explicit usage context would be helpful.

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/solomonneas/cortex-mcp'

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