Axint

axint.repair

Plan a project-aware Apple repair for existing apps. Indexes the local project, classifies build/UI/runtime evidence, runs Cloud Check when source is provided, ranks likely SwiftUI/App files, returns a host-aware patch/proof plan, and writes .axint/repair plus a privacy-safe .axint/feedback packet. Use: use for existing app bugs with logs, UI symptoms, or runtime evidence; not for greenfield generation. Inputs: describe the observed bug and attach logs or evidence; modifiedFiles and project index narrow the plan. Effects: writes .axint/repair and privacy-safe .axint/feedback artifacts; reads local project files.

Input Schema

TableJSON Schema

Name	Required	Description
`cwd`	No	Project directory. Defaults to the MCP process cwd.
`agent`	No	Active host/tool lane.
`issue`	Yes	The broken behavior or repair goal, e.g. 'comment box is visible but cannot be tapped'.
`format`	No	Output format. markdown returns the report, json returns structured data, and.
`source`	No	Optional inline Swift source for the suspected file.
`fileName`	No	Display file name when passing inline source.
`platform`	No	Target Apple platform hint.
`sourcePath`	No	Optional suspected Swift file path.
`testFailure`	No	Optional focused unit/UI-test failure text.
`writeReport`	No	Whether to write .axint/repair/latest.json and latest.md. Defaults to true.
`changedFiles`	No	Changed files to pin into the project context pack.
`writeFeedback`	No	Whether to write a privacy-safe .axint/feedback packet. Defaults to true.
`xcodeBuildLog`	No	Optional Xcode build/test log evidence.
`actualBehavior`	No	Optional observed behavior from the failing run.
`runtimeFailure`	No	Optional crash, freeze, hang, or runtime failure text.
`expectedBehavior`	No	Optional expected behavior for the failing feature.
`projectContextPath`	No	Optional .axint/context/latest.json path.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed6 schema fields changedJul 16, 2026

changedInput schema / properties / agent / description

Previous value: -"Active host/tool lane. Axint adapts the repair plan so Codex/Claude/Cursor avoid Xcode-only write tools."New value: +"Active host/tool lane."

changedInput schema / properties / format / description

Previous value: -"Output format. markdown returns the report, json returns structured data, and prompt returns the agent..."New value: +"Output format. markdown returns the report, json returns structured data, and."

changedInput schema / properties / source / description

Previous value: -"Optional inline Swift source for the suspected file. Source is not included in the feedback packet."New value: +"Optional inline Swift source for the suspected file."

changedInput schema / properties / sourcePath / description

Previous value: -"Optional suspected Swift file path. Axint reads it locally for Cloud Check and project anchoring."New value: +"Optional suspected Swift file path."

removedOutput schema / properties / isError / description

Removed value: -"Whether Axint marked the tool response as an error."

removedOutput schema / properties / text / description

Removed value: -"Primary Axint tool response text, matching the first text content block."

Changed11 schema fields changedMay 6, 2026

changedInput schema / properties / agent / description

Previous value: -"Active host/tool lane. Axint adapts the..."New value: +"Active host/tool lane. Axint adapts the repair plan so Codex/Claude/Cursor avoid Xcode-only write tools."

changedInput schema / properties / changedFiles / description

Previous value: -"Changed files to pin into the project..."New value: +"Changed files to pin into the project context pack."

changedInput schema / properties / cwd / description

Previous value: -"Project directory. Defaults to the MCP..."New value: +"Project directory. Defaults to the MCP process cwd."

changedInput schema / properties / expectedBehavior / description

Previous value: -"Optional expected behavior for the failing..."New value: +"Optional expected behavior for the failing feature."

changedInput schema / properties / format / description

Previous value: -"Output format. markdown returns the report,..."New value: +"Output format. markdown returns the report, json returns structured data, and prompt returns the agent..."

changedInput schema / properties / issue / description

Previous value: -"The broken behavior or repair goal, e.g...."New value: +"The broken behavior or repair goal, e.g. 'comment box is visible but cannot be tapped'."

changedInput schema / properties / runtimeFailure / description

Previous value: -"Optional crash, freeze, hang, or runtime..."New value: +"Optional crash, freeze, hang, or runtime failure text."

changedInput schema / properties / source / description

Previous value: -"Optional inline Swift source for the..."New value: +"Optional inline Swift source for the suspected file. Source is not included in the feedback packet."

changedInput schema / properties / sourcePath / description

Previous value: -"Optional suspected Swift file path. Axint..."New value: +"Optional suspected Swift file path. Axint reads it locally for Cloud Check and project anchoring."

changedInput schema / properties / writeFeedback / description

Previous value: -"Whether to write a privacy-safe .axint/feedba..."New value: +"Whether to write a privacy-safe .axint/feedback packet. Defaults to true."

changedInput schema / properties / writeReport / description

Previous value: -"Whether to write .axint/repair/latest.json..."New value: +"Whether to write .axint/repair/latest.json and latest.md. Defaults to true."

Changed19 schema fields changedMay 5, 2026

addedInput schema / properties / actualBehavior / description

Added value: +"Optional observed behavior from the failing run."

addedInput schema / properties / agent / description

Added value: +"Active host/tool lane. Axint adapts the..."

addedInput schema / properties / changedFiles / description

Added value: +"Changed files to pin into the project..."

addedInput schema / properties / changedFiles / items / description
```
Added value: +"String value for this Axint parameter."
```

addedInput schema / properties / cwd / description

Added value: +"Project directory. Defaults to the MCP..."

addedInput schema / properties / expectedBehavior / description

Added value: +"Optional expected behavior for the failing..."

addedInput schema / properties / fileName / description

Added value: +"Display file name when passing inline source."

addedInput schema / properties / format / description

Added value: +"Output format. markdown returns the report,..."

addedInput schema / properties / issue / description

Added value: +"The broken behavior or repair goal, e.g...."

addedInput schema / properties / platform / description
```
Added value: +"Target Apple platform hint."
```
addedInput schema / properties / projectContextPath / description
```
Added value: +"Optional .axint/context/latest.json path."
```

addedInput schema / properties / runtimeFailure / description

Added value: +"Optional crash, freeze, hang, or runtime..."

addedInput schema / properties / source / description

Added value: +"Optional inline Swift source for the..."

addedInput schema / properties / sourcePath / description

Added value: +"Optional suspected Swift file path. Axint..."

addedInput schema / properties / testFailure / description

Added value: +"Optional focused unit/UI-test failure text."

addedInput schema / properties / writeFeedback / description

Added value: +"Whether to write a privacy-safe .axint/feedba..."

addedInput schema / properties / writeReport / description

Added value: +"Whether to write .axint/repair/latest.json..."

addedInput schema / properties / xcodeBuildLog / description
```
Added value: +"Optional Xcode build/test log evidence."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "isError": {
+      "description": "Whether Axint marked the tool response as an error.",
+      "type": "boolean"
+    },
+    "text": {
+      "description": "Primary Axint tool response text, matching the first text content block.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text"
+  ],
+  "type": "object"
+}

AddedApr 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With all annotations false, the description carries the full burden. It clearly discloses side effects: 'reads local project files', 'writes .axint/repair and privacy-safe .axint/feedback artifacts', and even notes 'runs Cloud Check when source is provided', implying network activity. This exceeds the minimal disclosure expected.

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?

The description is structured into useful segments ('Use:', 'Inputs:', 'Effects:') and front-loads the main purpose. However, it repeats the artifact-writing detail ('writes .axint/repair plus a privacy-safe .axint/feedback packet' and later 'Effects: writes .axint/repair and privacy-safe .axint/feedback artifacts'), costing a small amount of economy.

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?

Despite having 17 parameters, the schema and output schema cover the detailed semantics. The description provides the high-level workflow (index, classify, Cloud Check, rank, return plan, write artifacts) and contextual notes (privacy-safe feedback, reads local files), making it complete for an agent to understand when and how to invoke the tool.

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 the baseline is 3. The description adds some context (e.g., 'describe the observed bug and attach logs or evidence', 'modifiedFiles and project index narrow the plan'), but it uses the term 'modifiedFiles' while the schema defines 'changedFiles', creating potential confusion. It doesn't meaningfully compensate beyond the schema's own descriptions.

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 clearly states the verb ('Plan'), the resource ('a project-aware Apple repair for existing apps'), and specific actions (indexes, classifies, runs Cloud Check, ranks files, returns plan, writes artifacts). It distinguishes from siblings by explicitly noting 'not for greenfield generation', separating it from scaffold or feature tools.

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?

The description provides explicit usage guidance: 'Use: use for existing app bugs with logs, UI symptoms, or runtime evidence; not for greenfield generation.' This is a clear when/when-not directive, and the mention of 'modifiedFiles and project index narrow the plan' indicates how to refine usage for better results.

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.repair

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources