Skip to main content
Glama
Stankye

AssemblyLine 4 MCP Server

by Stankye

al4_file_results

Retrieve all service analysis results for a file by providing its SHA256 hash. Get a comprehensive overview of the file's analysis from multiple services.

Instructions

Get all service analysis results for a file by SHA256.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sha256Yes

Implementation Reference

  • Input schema definition for the al4_file_results tool. Requires a 'sha256' string parameter.
    {
      name: "al4_file_results",
      description: "Get all service analysis results for a file by SHA256.",
      inputSchema: {
        type: "object",
        properties: {
          sha256: { type: "string" },
        },
        required: ["sha256"],
      },
    },
  • Handler case in the CallToolRequestSchema switch block. Calls client.getFileResults() with the sha256 argument.
    case "al4_file_results":
      result = await client.getFileResults(a.sha256 as string);
      break;
  • Client method getFileResults that makes a GET request to /api/v4/file/result/{sha256}/ to retrieve service analysis results for a file.
    getFileResults(
      sha256: string,
      opts?: RequestOptions,
    ): Promise<Record<string, unknown>> {
      if (!SHA256_RE.test(sha256)) throw new Error(`Invalid sha256: ${sha256}`);
      return this.requestJson(
        "GET",
        `/api/v4/file/result/${seg(sha256)}/`,
        undefined,
        opts,
      );
    }
Behavior2/5

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

No annotations are provided, so description carries full burden. It does not disclose the structure of results (e.g., list of scans), pagination, or whether it is read-only. Only states it returns 'results'.

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 redundancy. Efficient for purpose, but lacks structure (e.g., no bullet points or parameter details).

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?

With 1 parameter and no output schema, the description is too minimal. It could specify the type of results (e.g., from all engines) and how to interpret them. Sibling tools exist but no differentiation is provided.

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?

Schema has 0% description coverage. Description does not add any meaning beyond parameter name 'sha256'. No format (hex, length) or example provided.

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?

Description clearly states it retrieves all service analysis results for a file by SHA256. Verb 'Get' and resource 'service analysis results' are specific, and it distinguishes from siblings like al4_file_info (info) and al4_file_score (score).

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 such as al4_search_results or al4_submission_summary. Agent must infer based on tool name.

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/Stankye/vibe-assemblylinev4-mcp'

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