Skip to main content
Glama
Ada MCP Server

Ada MCP Server

ada_build

Compiles an Ada project with GPRbuild and returns compilation results. Supports optional clean, target, project file, and extra build arguments.

Instructions

Build an Ada project using GPRbuild and return compilation results

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": "ada_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
cleanNoClean before building
targetNoSpecific build target (main unit name)
gpr_fileNoPath to GPR project file (auto-detects if not provided)
extra_argsNoAdditional arguments to pass to gprbuild

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It discloses only that GPRbuild is invoked and compilation results are returned; it says nothing about side effects (writing object/artifact files into the project tree), whether 'clean' deletes prior build output, expected duration/timeouts, or whether a failed build raises an error versus returning errors in the response.

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 sentence with no filler or repetition. It is efficient, though the brevity partly reflects under-specification rather than disciplined editing.

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 four-parameter build tool with no output schema and no annotations, the description is only minimally adequate. It confirms the return value is compilation results, but does not cover side effects, clean's destructive nature, or failure behavior, which an agent needs to invoke it safely.

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 description coverage is 100%, so every parameter including clean, target, gpr_file, and extra_args is already documented in the schema. The description adds no extra meaning such as accepted target syntax or example extra_args values, so the baseline 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 (Build) and resource (Ada project) plus the underlying driver (GPRbuild) and outcome (compilation results). It is clearly distinguishable from the sibling LSP tools (hover, diagnostics, rename), none of which compile. It stops short of distinguishing from a hypothetical run/test tool, but within this catalog the purpose is unambiguous.

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 explicit when-to-use guidance, no prerequisite conditions (e.g. project must be configured, gpr file must exist), and no mention of when not to run a full build versus using ada_diagnostics for a quick check. Usage is only implied by the verb 'build'.

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