Axint

axint.run

Run the enforced Axint Apple build loop outside the Xcode UI. Use: use for the complete proof loop; use swift.validate, cloud.check, or fix-packet when only one stage is needed. Inputs: integration=minimal enforces local advisory no-fix behavior; background returns a job id; outputDir controls artifacts. Effects: starts child processes, writes .axint/run artifacts, may run xcodebuild/tests, and may call Cloud Check.

Input Schema

TableJSON Schema

Name	Required	Description
`cwd`	No	Project directory to run. Defaults to the MCP process cwd.
`fix`	No	Allow automatic fix behavior. Forced false by minimal mode.
`agent`	No	Current agent host lane.
`dryRun`	No	Plan xcodebuild commands without executing them.
`format`	No	Output format. markdown returns the run report, json returns structured data.
`scheme`	No	Xcode scheme. If omitted, Axint tries to infer one.
`project`	No	Path to .xcodeproj, relative to cwd or absolute.
`runtime`	No	After build, launch the built macOS .app and capture runtime/timeout evidence.
`advisory`	No	Keep unconfirmed static findings non-blocking while preserving them in the.
`platform`	No	Target Apple platform. Defaults to macOS unless inferred from destination.
`testPlan`	No	Optional xcodebuild -testPlan for test runs.
`localOnly`	No	Deny hosted/network checks for this run.
`outputDir`	No	Explicit artifact directory.
`skipBuild`	No	Skip xcodebuild build and only run Axint static gates.
`skipTests`	No	Skip xcodebuild test.
`workspace`	No	Path to .xcworkspace, relative to cwd or absolute.
`background`	No	Start the run and immediately return a resumable job id instead of waiting for.
`destination`	No	xcodebuild destination, e.g. platform=macOS or platform=iOS.
`integration`	No	Execution profile. minimal denies network/project mutation, disables automatic.
`onlyTesting`	No	Optional focused xcodebuild -only-testing selectors, e.g.
`projectName`	No	Project name for Axint session and report labels.
`writeReport`	No	Whether to write .axint/run/latest.json and latest.md. Defaults to true.
`configuration`	No	Xcode build configuration, e.g. Debug or Release.
`includeSource`	No	Include full Swift source and full command output in json output.
`modifiedFiles`	No	Changed Swift files to validate and Cloud Check.
`actualBehavior`	No	Actual runtime behavior for semantic bug checks.
`runtimeFailure`	No	Crash, freeze, hang, launch timeout, or UI failure evidence.
`timeoutSeconds`	No	Build/test timeout in seconds.
`derivedDataPath`	No	Optional xcodebuild -derivedDataPath.
`expectedVersion`	No	Expected Axint package version for the run session.
`expectedBehavior`	No	Expected runtime behavior for semantic bug checks.
`runtimeTimeoutSeconds`	No	Runtime launch timeout in seconds.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes
`isError`	No

TDQS

A4.9/5.0

Behavior5/5

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

The description discloses concrete side effects: 'starts child processes, writes .axint/run artifacts, may run xcodebuild/tests, and may call Cloud Check.' This complements the annotations (readOnlyHint=false, openWorldHint=true) and adds useful specifics about artifact paths and external calls, going beyond what annotations already convey.

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?

The description is composed of three tightly focused sentences: purpose, usage guidance, and effects. It is front-loaded with the action and resource, every sentence earns its place, and there is zero redundancy or filler.

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

Completeness5/5

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

Given the tool's complexity (32 parameters, output schema, annotations), the description provides a complete high-level orientation. It names sibling tools for alternatives, mentions background execution and artifacts, and leaves parameter-level details to the comprehensive schema. An agent has enough context to select and invoke this tool correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds interpretive value by explaining the behavioral impact of key parameters (e.g., 'integration=minimal enforces local advisory no-fix behavior' goes beyond the schema's wording). This elevates it to a 4, though the schema remains the primary source for parameter details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Run the enforced Axint Apple build loop outside the Xcode UI,' which clearly identifies the action, resource, and context. It then distinguishes from siblings by naming alternatives (swift.validate, cloud.check, fix-packet) when only one stage is needed, leaving no ambiguity about its primary role.

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

Usage Guidelines5/5

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

Explicitly states 'Use for the complete proof loop' and directly instructs when to use alternatives ('use swift.validate, cloud.check, or fix-packet when only one stage is needed'). It also highlights key configuration modes (integration, background, outputDir) that affect how the tool is invoked.

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

All Axint tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, with descriptions specifying exact use cases (e.g., axint.activate for smoke test, axint.status for version). There is minor potential overlap between axint.suggest and axint.feature, but descriptions clarify suggestion vs generation.

Naming Consistency5/5

All tools follow a consistent hierarchical pattern: 'axint.<category>.<action>' (e.g., axint.agent.advice, axint.swift.validate). Even standalone tools like axint.compile fit the pattern. No mixing of conventions.

Tool Count2/5

36 tools is well above the typical 3-15 range for a well-scoped set. While the server covers a broad domain, the sheer number may overwhelm agents and reduce efficiency. A reduction or grouping would improve coherence.

Completeness4/5

The tool set covers the full Axint development lifecycle: installation, compilation, validation, repair, upgrade, session management, and coordination. Minor gaps exist (e.g., no dedicated tool for deleting project artifacts), but core workflows are well-supported.

axint.run

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources