Skip to main content
Glama

axint.repair

Diagnose and fix existing app bugs by analyzing project files, build logs, UI symptoms, and runtime errors. Provides a ranked repair plan with privacy-safe feedback artifacts.

Instructions

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... Use: use for existing app bugs with logs, UI symptoms, or runtime evidence; not for greenfield generation. Effects: writes .axint/repair and privacy-safe .axint/feedback artifacts; reads local project files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoProject directory. Defaults to the MCP process cwd.
issueYesThe broken behavior or repair goal, e.g. 'comment box is visible but cannot be tapped'.
sourceNoOptional inline Swift source for the suspected file. Source is not included in the feedback packet.
sourcePathNoOptional suspected Swift file path. Axint reads it locally for Cloud Check and project anchoring.
fileNameNoDisplay file name when passing inline source.
platformNoTarget Apple platform hint.
agentNoActive host/tool lane. Axint adapts the repair plan so Codex/Claude/Cursor avoid Xcode-only write tools.
expectedBehaviorNoOptional expected behavior for the failing feature.
actualBehaviorNoOptional observed behavior from the failing run.
xcodeBuildLogNoOptional Xcode build/test log evidence.
testFailureNoOptional focused unit/UI-test failure text.
runtimeFailureNoOptional crash, freeze, hang, or runtime failure text.
changedFilesNoChanged files to pin into the project context pack.
projectContextPathNoOptional .axint/context/latest.json path.
writeReportNoWhether to write .axint/repair/latest.json and latest.md. Defaults to true.
writeFeedbackNoWhether to write a privacy-safe .axint/feedback packet. Defaults to true.
formatNoOutput format. markdown returns the report, json returns structured data, and prompt returns the agent...

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 provide no safety hints, so the description carries the burden. It discloses effects: writes .axint/repair and .axint/feedback artifacts, reads project files. This is clear, though it could mention if network is used (Cloud Check implies it).

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 concise with clear sections (Use, Effects) and front-loaded information. However, the final sentence is truncated ('returns a...'), slightly reducing clarity.

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

Completeness4/5

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

Given the tool's complexity (17 params, output schema exists), the description covers purpose, use cases, and effects. It could mention that it does not modify source code, but the overall context is adequate.

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 baseline is 3. The description adds value by explaining how 'source' triggers Cloud Check and how the tool indexes and ranks files, giving context beyond parameter names.

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 starts with a specific verb+resource ('Plan a project-aware Apple repair for existing apps'), lists key actions (index, classify, run Cloud Check), and distinguishes from siblings by explicitly excluding greenfield generation.

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 'Use:' section explicitly states when to use ('existing app bugs with logs, UI symptoms, or runtime evidence') and when not to ('not for greenfield generation'), providing clear context for selection among siblings.

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