Skip to main content
Glama

Axint

by io.github.agenticempire

axint.upgrade

Destructive

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
NameRequiredDescriptionDefault
cwdNoProject directory where .axint/upgrade/latest.* should be written.
applyNoWhether to install the target package.
formatNoOutput format. markdown is human-readable, json is structured, and prompt is.
writeReportNoWhether to write .axint/upgrade/latest.json and latest.md.
latestVersionNoKnown latest version to compare against.
targetVersionNoSpecific Axint version to install. Defaults to the latest published npm version.
reinstallXcodeNoWhether apply mode should also refresh optional Xcode MCP wiring.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
isErrorNo

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.

All Axint toolsInspect
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.

Resources