Skip to main content
Glama

get_last_build_status

Check the status of your last ClojureScript build to verify if it succeeded or failed, including any warnings or errors.

Instructions

Get the status of the last shadow-cljs build including any warnings or errors. Call this after making edits to ClojureScript files to verify if the build succeeded or failed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.js:36-47 (handler)
    The core handler function of the 'get_last_build_status' tool. It returns the last recorded build status (stored in this.lastBuildStatus) or a default 'unknown' status, augmented with the current WebSocket connection status.
    getLastBuildStatus() {
      const status = this.lastBuildStatus || {
        status: 'unknown',
        message: 'No build status available yet',
        timestamp: new Date().toISOString()
      };
      
      return {
        ...status,
        websocket_connected: this.connected
      };
    }
  • index.js:260-272 (registration)
    Registers the 'get_last_build_status' tool in the MCP ListTools response, providing its name, description, and input schema (empty object).
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        {
          name: "get_last_build_status",
          description: "Get the status of the last shadow-cljs build including any warnings or errors. Call this after making edits to ClojureScript files to verify if the build succeeded or failed.",
          inputSchema: {
            type: "object",
            properties: {},
            required: []
          }
        }
      ]
    }));
  • The MCP CallTool request handler that executes the 'get_last_build_status' tool by invoking this.monitor.getLastBuildStatus() and returning the result as JSON text content.
      this.server.setRequestHandler(CallToolRequestSchema, async (request) => {
        if (!request.params || request.params.name !== "get_last_build_status") {
          throw new McpError(ErrorCode.MethodNotFound, `Unknown tool: ${request.params?.name || 'undefined'}`);
        }
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(this.monitor.getLastBuildStatus(), null, 2)
            }
          ]
        };
      });
    }
  • The input schema for the 'get_last_build_status' tool, which expects no parameters (empty object).
    inputSchema: {
      type: "object",
      properties: {},
      required: []
    }
Behavior4/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 effectively describes the tool's behavior: it retrieves build status and includes warnings/errors, which is useful for understanding output. However, it doesn't mention potential side effects, error handling, or response format details, leaving some behavioral aspects unspecified.

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?

The description is two sentences that are front-loaded with the tool's purpose and followed by usage guidance. Every sentence adds value without redundancy, making it appropriately sized and efficient.

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?

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is mostly complete. It explains what the tool does and when to use it. However, without an output schema, it could benefit from more detail on the return format (e.g., what 'status' includes), but this is a minor gap for such a straightforward tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't discuss parameters, which is appropriate. A baseline of 4 is applied since no parameters exist, and the description doesn't add unnecessary information.

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 specific action ('Get the status'), target resource ('last shadow-cljs build'), and scope ('including any warnings or errors'). It precisely defines what the tool does without being tautological or vague, and since there are no sibling tools, no differentiation is needed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool: 'Call this after making edits to ClojureScript files to verify if the build succeeded or failed.' This provides clear context and timing guidance. Since there are no sibling tools, no alternative comparisons are necessary.

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/Bigsy/shadow-cljs-mcp'

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