axint

axint.upgrade

Destructive

Check the latest Axint package version and optionally upgrade the server while preserving the current agent thread. Use when the server status shows staleness.

Instructions

Check the latest Axint package and optionally apply the upgrade while preserving the current agent thread. Use: call when axint.status shows a stale server; not for app dependency upgrades. Inputs: apply defaults false; targetVersion selects the install, while reinstallXcode and writeReport matter only when applying. Effects: destructive when apply=true: can run package installs, refresh Xcode wiring, and write .axint/upgrade; may use npm.

Input Schema

TableJSON Schema

Name	Required	Description
`cwd`	No	Project directory where .axint/upgrade/latest.* should be written.
`apply`	No	Whether to install the target package.
`format`	No	Output format. markdown is human-readable, json is structured, and prompt is.
`writeReport`	No	Whether to write .axint/upgrade/latest.json and latest.md.
`latestVersion`	No	Known latest version to compare against.
`targetVersion`	No	Specific Axint version to install. Defaults to the latest published npm version.
`reinstallXcode`	No	Whether apply mode should also refresh optional Xcode MCP wiring.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedJul 7, 2026

changedInput schema / properties / apply / description

Previous value: -"Whether to instal..."New value: +"Whether to install the target package."

changedInput schema / properties / cwd / description

Previous value: -"Project directory..."New value: +"Project directory where .axint/upgrade/latest.* should be written."

changedInput schema / properties / format / description

Previous value: -"Output format. ma..."New value: +"Output format. markdown is human-readable, json is structured, and prompt is."

changedInput schema / properties / latestVersion / description

Previous value: -"Known latest vers..."New value: +"Known latest version to compare against."

changedInput schema / properties / reinstallXcode / description

Previous value: -"Whether apply mod..."New value: +"Whether apply mode should also refresh optional Xcode MCP wiring."

changedInput schema / properties / targetVersion / description

Previous value: -"Specific Axint ve..."New value: +"Specific Axint version to install. Defaults to the latest published npm version."

changedInput schema / properties / writeReport / description

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

Changed9 schema fields changedv0.4.34Jul 7, 2026

changedInput schema / properties / apply / description

Previous value: -"Whether to install the target package. Defaults to false, which only returns the plan."New value: +"Whether to instal..."

changedInput schema / properties / cwd / description

Previous value: -"Project directory where .axint/upgrade/latest.* should be written. Defaults to the MCP process cwd."New value: +"Project directory..."

changedInput schema / properties / format / description

Previous value: -"Output format. markdown is human-readable, json is structured, and prompt is the continuation block."New value: +"Output format. ma..."

changedInput schema / properties / latestVersion / description

Previous value: -"Known latest version to compare against. Useful for deterministic agent tests or offline planning."New value: +"Known latest vers..."

changedInput schema / properties / reinstallXcode / description

Previous value: -"Whether apply mode should also refresh optional Xcode MCP wiring. Defaults to false."New value: +"Whether apply mod..."

changedInput schema / properties / targetVersion / description

Previous value: -"Specific Axint version to install. Defaults to the latest published npm version."New value: +"Specific Axint ve..."

changedInput schema / properties / writeReport / description

Previous value: -"Whether to write .axint/upgrade/latest.json and latest.md. Defaults to true when apply is true."New value: +"Whether to write..."

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

Changed7 schema fields changedv0.4.28May 6, 2026

changedInput schema / properties / apply / description

Previous value: -"Whether to install the target package...."New value: +"Whether to install the target package. Defaults to false, which only returns the plan."

changedInput schema / properties / cwd / description

Previous value: -"Project directory where .axint/upgrade/latest..."New value: +"Project directory where .axint/upgrade/latest.* should be written. Defaults to the MCP process cwd."

changedInput schema / properties / format / description

Previous value: -"Output format. markdown is human-readable,..."New value: +"Output format. markdown is human-readable, json is structured, and prompt is the continuation block."

changedInput schema / properties / latestVersion / description

Previous value: -"Known latest version to compare against...."New value: +"Known latest version to compare against. Useful for deterministic agent tests or offline planning."

changedInput schema / properties / reinstallXcode / description

Previous value: -"Whether apply mode should also refresh..."New value: +"Whether apply mode should also refresh optional Xcode MCP wiring. Defaults to false."

changedInput schema / properties / targetVersion / description

Previous value: -"Specific Axint version to install. Defaults..."New value: +"Specific Axint version to install. Defaults to the latest published npm version."

changedInput schema / properties / writeReport / description

Previous value: -"Whether to write .axint/upgrade/latest.json..."New value: +"Whether to write .axint/upgrade/latest.json and latest.md. Defaults to true when apply is true."

Addedv0.4.26May 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Adds detailed effects beyond annotations: destructive operations when apply=true (package installs, Xcode wiring refresh, writing .axint/upgrade), plus preserving agent thread and potential npm usage, providing concrete behavioral context.

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 structured with clear sections and front-loaded purpose, though it packs many details into a dense block; still efficient.

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?

For a tool with 7 params, annotations, and output schema, the description covers purpose, usage triggers, exclusions, effects, and parameter relationships, leaving no major gaps.

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

Parameters5/5

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

Schema covers all 7 params, and description adds conditional semantics (apply defaults false; targetVersion vs reinstallXcode/writeReport applicability), helping agents correctly configure calls.

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?

Description clearly states the tool checks the latest Axint package and optionally applies the upgrade, with a specific use case (stale server) and exclusions (not for app dependency upgrades), distinguishing it from sibling status/install tools.

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?

Explicitly says when to call (axint.status shows stale server) and when not to (app dependency upgrades), but doesn't name a specific alternative tool, so not quite a 5.

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

axint.upgrade

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools