Skip to main content
Glama
Stankye

AssemblyLine 4 MCP Server

by Stankye

al4_whoami

Retrieves account details for the authenticated user on the AssemblyLine platform.

Instructions

Return details about the currently authenticated AssemblyLine user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler method `whoami()` on the AL4Client class that performs the API call to GET /api/v4/user/whoami/ and returns user data.
    whoami(opts?: RequestOptions): Promise<Record<string, unknown>> {
      return this.requestJson("GET", "/api/v4/user/whoami/", undefined, opts);
    }
  • Tool registration schema for al4_whoami: defines name, description, and empty inputSchema (no parameters required).
    const TOOLS = [
      {
        name: "al4_whoami",
        description: "Return details about the currently authenticated AssemblyLine user.",
        inputSchema: { type: "object", properties: {}, required: [] },
      },
  • src/index.ts:381-383 (registration)
    The switch-case handler in the CallToolRequestSchema that dispatches 'al4_whoami' to client.whoami().
    case "al4_whoami":
      result = await client.whoami();
      break;
Behavior4/5

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

No annotations are provided, so the description carries full burden. It states the tool returns user details, implying a read-only operation. No contradictions or misleading statements; adequate for a simple query tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence that is clear and front-loaded. Every word serves a purpose; no wasted content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool is simple with no output schema. Description conveys the essential purpose. It could hint at return details, but given low complexity, it is sufficiently complete.

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 no parameters, and schema description coverage is 100%. Description adds no parameter information beyond schema, meeting the baseline of 3 as per rubric.

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 the tool returns details about the currently authenticated AssemblyLine user. Verb 'Return' and resource 'details about the currently authenticated user' are specific and distinct from sibling tools that deal with files, alerts, or submissions.

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 does not explicitly provide when or when not to use this tool or mention alternatives. The intended usage is implied by the tool name and purpose, but no direct guidance is given.

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