Skip to main content
Glama
Stankye

AssemblyLine 4 MCP Server

by Stankye

al4_submission_full

Retrieve the complete results tree for a finished submission to access all service results and scores.

Instructions

Get the complete results tree for a finished submission, including all service results and scores.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sidYes

Implementation Reference

  • src/index.ts:167-178 (registration)
    Tool registration for al4_submission_full — defines name, description, and inputSchema (requires sid string).
    {
      name: "al4_submission_full",
      description:
        "Get the complete results tree for a finished submission, including all service results and scores.",
      inputSchema: {
        type: "object",
        properties: {
          sid: { type: "string" },
        },
        required: ["sid"],
      },
    },
  • Handler dispatch: calls client.getSubmissionFull(a.sid as string) when tool name is 'al4_submission_full'.
    case "al4_submission_full":
      result = await client.getSubmissionFull(a.sid as string);
      break;
  • getSubmissionFull method on AL4Client: validates sid, sends GET /api/v4/submission/full/{sid}/, returns the complete results tree.
    getSubmissionFull(
      sid: string,
      opts?: RequestOptions,
    ): Promise<Record<string, unknown>> {
      if (!sid) throw new Error("sid is required");
      return this.requestJson(
        "GET",
        `/api/v4/submission/full/${seg(sid)}/`,
        undefined,
        opts,
      );
    }
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It merely states what the tool does ('get'), but does not mention potential side effects, required permissions, rate limits, or behavior on non-finished submissions. This is insufficient for safe invocation.

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, clear sentence that front-loads the key action and scope. It is concise without being cryptic, though it could be more information-dense without losing conciseness.

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 lack of annotations and output schema, the description is too minimal. It does not clarify what the 'complete results tree' entails in terms of structure or content, nor does it differentiate effectively from sibling tools like al4_submission_get or al4_search_results. Significant gaps remain for an agent to use this tool correctly.

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?

The single parameter 'sid' has no description in the schema (0% coverage), and the tool description adds no explanation about what 'sid' represents (e.g., submission ID). The description fails to provide any additional meaning beyond the parameter name.

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

Purpose4/5

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

The description clearly states the tool retrieves the complete results tree for a finished submission, including service results and scores. It distinguishes from siblings like al4_submission_get (likely simpler) and al4_submission_summary (summary only) by specifying 'complete results tree' and 'finished submission', but does not explicitly differentiate from all similar tools.

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 usage only when the submission is finished ('for a finished submission'), which provides context, but it does not explicitly state when not to use it (e.g., for in-progress submissions) or mention alternatives like al4_submission_get or al4_submission_summary.

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