Skip to main content
Glama

axint.run

Runs the Apple build loop outside Xcode UI to validate Swift, perform Cloud Check, and execute xcodebuild build/test for proof of correctness.

Instructions

Run the enforced Axint Apple build loop outside the Xcode UI. Starts or refreshes the Axint session, validates Swift, runs Cloud Check, executes xcodebuild build/test when a project or workspace... Use: use when the agent must prove Swift validation, Cloud Check, Xcode build/test, and runtime evidence. Effects: starts child processes, writes .axint/run artifacts, may run xcodebuild/tests, and may call Cloud Check.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoProject directory to run. Defaults to the MCP process cwd.
projectNameNoProject name for Axint session and report labels.
expectedVersionNoExpected Axint package version for the run session.
platformNoTarget Apple platform. Defaults to macOS unless inferred from destination.
agentNoCurrent agent host lane. Axint uses this to start the right session profile and return host-safe repair...
schemeNoXcode scheme. If omitted, Axint tries to infer one.
workspaceNoPath to .xcworkspace, relative to cwd or absolute.
projectNoPath to .xcodeproj, relative to cwd or absolute.
destinationNoxcodebuild destination, e.g. platform=macOS or platform=iOS Simulator,name=iPhone 16.
configurationNoXcode build configuration, e.g. Debug or Release.
derivedDataPathNoOptional xcodebuild -derivedDataPath.
testPlanNoOptional xcodebuild -testPlan for test runs.
onlyTestingNoOptional focused xcodebuild -only-testing selectors, e.g....
modifiedFilesNoChanged Swift files to validate and Cloud Check. Pass this whenever possible; if omitted, Axint validates...
skipBuildNoSkip xcodebuild build and only run Axint static gates.
skipTestsNoSkip xcodebuild test.
runtimeNoAfter build, launch the built macOS .app and capture runtime/timeout evidence.
runtimeTimeoutSecondsNoRuntime launch timeout in seconds.
timeoutSecondsNoBuild/test timeout in seconds.
expectedBehaviorNoExpected runtime behavior for semantic bug checks.
actualBehaviorNoActual runtime behavior for semantic bug checks.
runtimeFailureNoCrash, freeze, hang, launch timeout, or UI failure evidence.
dryRunNoPlan xcodebuild commands without executing them.
writeReportNoWhether to write .axint/run/latest.json and latest.md. Defaults to true.
backgroundNoStart the run and immediately return a resumable job id instead of waiting for long Xcode build, test, or...
includeSourceNoInclude full Swift source and full command output in json output. Defaults to false so long agent threads...
formatNoOutput format. markdown returns the run report, json returns structured data, prompt returns only the repair...

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesPrimary Axint tool response text, matching the first text content block.
isErrorNoWhether Axint marked the tool response as an error.
Behavior4/5

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

Annotations are sparse (no readOnly, destructive, idempotent hints); the description compensates by listing effects: starts child processes, writes artifacts, may run xcodebuild/tests and Cloud Check. This adds useful behavioral context beyond annotations.

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?

Description is concise with clear sections (purpose, use, effects). It is front-loaded with the primary action and succinct, though could be slightly more structured.

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?

Given the complexity (27 parameters, output schema, annotations), the description provides adequate purpose and effects but lacks guidance on parameter interplay or common patterns. Sufficient but not outstanding.

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?

All 27 parameters are described in the schema (100% coverage), so the description adds little beyond general workflow context. Baseline of 3 appropriate as schema does heavy lifting.

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?

The description clearly states the tool runs the Axint Apple build loop, listing specific steps like Swift validation and Cloud Check. It distinguishes the full build loop from sibling tools, though it does not explicitly contrast with them.

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?

The 'Use:' section provides a clear scenario: when the agent must prove Swift validation, Cloud Check, Xcode build/test, and runtime evidence. However, it does not explicitly exclude when to use alternatives like axint.swift.validate.

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/agenticempire/axint'

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