Skip to main content
Glama

Build Project

varity_build
Idempotent

Builds Node.js or Python projects for production by auto-detecting the framework from package.json, so you can verify compilation before deployment.

Instructions

Build the project for production. Auto-detects framework from package.json. Run before deploying or to verify the project compiles.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "varity_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoPath to the project directory (default: current directory)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0-beta.24

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare the operation is non-read-only but idempotent and non-destructive, so the safety profile is covered. The description adds genuine context with framework auto-detection and the production target, but says nothing about build artifacts location, expected duration, or how failures surface. Useful addition, not rich behavioral disclosure.

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?

Three short sentences with zero filler, and the core action is front-loaded before the mechanism and the usage note. Every sentence carries distinct information.

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?

For a low-complexity, single-optional-parameter tool with annotations covering its safety profile and no output schema, the description covers what to expect and when to call it. Minor gap: no mention of where build output lands or what a successful result looks like.

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?

Schema coverage is 100% and the single path parameter is fully documented with its default in the schema. The description adds no meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ('Build the project for production') plus a distinguishing mechanism ('Auto-detects framework from package.json'). An agent can separate this from varity_deploy or varity_dev_server by the production-compile framing, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

Gives clear invocation context: 'Run before deploying or to verify the project compiles.' That covers both the pre-deploy workflow and a standalone verification use case. It stops short of explicit exclusions or naming an alternative tool for what to do after a failed build.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.