Skip to main content
Glama

builds_release_disk

Free disk: drop deps/caches/serving tree; keeps source/revisions/routes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "build_id": "<build_id>"
    },
    "name": "builds_release_disk"
  }
}

Input Schema

NameRequiredDescriptionDefault
build_idYes
workspaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds the crucial detail that dependencies, caches and the serving tree are removed while source, revisions and routes survive. That reconciles with destructiveHint=false (only regenerable artifacts are lost) and tells the agent the operation is not fully reversible without a rebuild. It does not say whether the build must be stopped first or how long re-provisioning takes.

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?

A single front-loaded fragment with the destructive part first and the preservation guarantee second; no filler. The telegraphic style ("deps", "serving tree") is efficient but slightly opaque.

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

Completeness3/5

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

For a no-output-schema disk-cleanup tool the description covers the main risk surface (what is dropped vs kept), but leaves parameter meaning, preconditions, and post-state (does the build still serve?) unaddressed. Adequate to call, thin on operational consequences.

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

Parameters2/5

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

Both parameters (workspace, build_id) have 0% schema description coverage, so the description carries the full burden — yet it says nothing about what workspace scoping means or how build_id is validated. The UUID format is only visible in the schema.

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?

"Free disk: drop deps/caches/serving tree; keeps source/revisions/routes" names a concrete action and enumerates the artifacts affected, so the agent knows this reclaims space by deleting regenerable build output. It stops short of distinguishing itself from siblings like builds_archive, but the verb+resource is specific enough to select on.

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?

There is no when-to-use guidance, no preconditions (e.g. build must not be actively serving), and no pointer to alternatives. The agent must infer that this is a cleanup operation to run when disk pressure exists.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources