Skip to main content
Glama
Ada MCP Server

Ada MCP Server

ada_format_file

Formats Ada source files using GNATformat and configurable indentation options to keep code consistently styled and easier to read.

Instructions

Format an Ada source file using GNATformat

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": {
      "file": "<file>"
    },
    "name": "ada_format_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesAbsolute path to the Ada file
tab_sizeNoTab width (default 3 for Ada)
insert_spacesNoUse spaces instead of tabs

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 provided, so the description carries the full burden, yet it never says whether the file is rewritten in place or formatted content is returned, whether formatting is idempotent, or how syntax errors are handled. 'Format' implies mutation of a source file, which is a consequential behavior left undisclosed.

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?

A single front-loaded sentence with zero filler; the verb, resource, and tool are all in the first few words. Nothing is wasted, though the brevity is also the source of the definition's gaps.

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

Completeness2/5

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

For a mutating file operation with no annotations and no output schema, the description leaves the most important questions unanswered: in-place modification vs. returned text, and what happens on failure. The schema is complete, but the behavioral picture is not.

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 all three parameters (file, tab_size, insert_spaces) are already documented with defaults and meaning. The description adds no further parameter guidance, which is acceptable at baseline when the schema is this complete.

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 (format an Ada source file) plus the underlying formatter (GNATformat), which clearly separates it from the read-only navigation siblings like ada_hover or ada_document_symbols. It stops short of saying what the output of formatting is, but an agent can identify the operation without opening the schema.

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?

No guidance on when to call this versus other tools, no prerequisites (e.g., whether a project or GNATformat binary must exist), and no note about when formatting is inappropriate. The agent must infer all of this.

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