Skip to main content
Glama

axint.upgrade

Destructive

Check and optionally upgrade the server package when stale, preserving the agent thread. Returns install commands and can refresh Xcode wiring.

Instructions

Check the latest Axint package and optionally apply the upgrade while preserving the current agent thread. Returns exact install commands, optional Xcode MCP wiring refresh, .axint/upgrade/latest.*... Use: call when axint.status shows a stale server; not for app dependency upgrades. Effects: destructive when apply=true: can run package installs, refresh Xcode wiring, and write .axint/upgrade; may use npm network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoProject directory where .axint/upgrade/latest.* should be written. Defaults to the MCP process cwd.
targetVersionNoSpecific Axint version to install. Defaults to the latest published npm version.
latestVersionNoKnown latest version to compare against. Useful for deterministic agent tests or offline planning.
applyNoWhether to install the target package. Defaults to false, which only returns the plan.
reinstallXcodeNoWhether apply mode should also refresh optional Xcode MCP wiring. Defaults to false.
writeReportNoWhether to write .axint/upgrade/latest.json and latest.md. Defaults to true when apply is true.
formatNoOutput format. markdown is human-readable, json is structured, and prompt is the continuation block.

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?

Beyond annotations (destructiveHint=true), the description adds that it can run package installs, refresh Xcode wiring, and write to .axint/upgrade, plus 'preserving the current agent thread.' This provides useful 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?

Front-loaded with purpose, then output summary, then usage and effects. Slightly verbose but every sentence adds value. Good structure.

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 output schema exists, the description adequately covers purpose, usage, param context, and effects. No major gaps.

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?

All 7 parameters have full schema descriptions (100% coverage), so baseline is 3. The description adds value by summarizing the output format and destinations, exceeding baseline.

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 it checks and optionally applies Axint upgrades, with a specific verb-resource pairing. It distinguishes from siblings by stating 'not for app dependency upgrades', making its scope unambiguous.

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 says 'call when axint.status shows a stale server' and excludes app dependency upgrades, providing clear when-to-use and when-not-to-use guidance.

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