Skip to main content
Glama
agenticempire

axint

by agenticempire
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Hybrid

axint.project.syncVersion

Idempotent

Update project-pack version hints in Axint-owned files after package upgrades, ensuring agent instructions reference the correct version.

Instructions

Update Axint-owned project-pack version hints after an upgrade. Use this after axint.upgrade or npm/pip upgrades so .axint/project.json, AGENTS.md, CLAUDE.md, and Axint rehydration docs stop pointing agents at an older package version. Use: use after package upgrades so local project-pack hints stop naming old Axint versions. Inputs: cwd scopes Axint-owned files; targetVersion overrides running version; dryRun prevents writes. Effects: updates Axint-owned project instruction files unless dryRun=true; no network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNoWhen true, reports the files that would change without writing them.
formatNoOutput format. Defaults to markdown.
versionNoAxint version to write. Defaults to the running MCP server version.
targetDirNoProject directory to update. Defaults to the current working directory.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
isErrorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / dryRun / description
      Previous value: -"When true, report..."New value: +"When true, reports the files that would change without writing them."
    • changedInput schema / properties / format / description
      Previous value: -"Output format. De..."New value: +"Output format. Defaults to markdown."
    • changedInput schema / properties / targetDir / description
      Previous value: -"Project directory..."New value: +"Project directory to update. Defaults to the current working directory."
    • changedInput schema / properties / version / description
      Previous value: -"Axint version to..."New value: +"Axint version to write. Defaults to the running MCP server version."
  2. Changed6 schema fields changedv0.4.34
    • changedInput schema / properties / dryRun / description
      Previous value: -"When true, reports the files that would change without writing them."New value: +"When true, report..."
    • changedInput schema / properties / format / description
      Previous value: -"Output format. Defaults to markdown."New value: +"Output format. De..."
    • changedInput schema / properties / targetDir / description
      Previous value: -"Project directory to update. Defaults to the current working directory."New value: +"Project directory..."
    • changedInput schema / properties / version / description
      Previous value: -"Axint version to write. Defaults to the running MCP server version."New value: +"Axint version to..."
    • 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."
  3. Changed3 schema fields changedv0.4.28
    • changedInput schema / properties / dryRun / description
      Previous value: -"When true, reports the files that would..."New value: +"When true, reports the files that would change without writing them."
    • changedInput schema / properties / targetDir / description
      Previous value: -"Project directory to update. Defaults to the..."New value: +"Project directory to update. Defaults to the current working directory."
    • changedInput schema / properties / version / description
      Previous value: -"Axint version to write. Defaults to the..."New value: +"Axint version to write. Defaults to the running MCP server version."
  4. Addedv0.4.26

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses that the tool writes to Axint-owned project instruction files, honors dryRun to suppress writes, and makes no network calls. Annotations already indicate non-read-only and non-destructive behavior, and the description aligns with and extends them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is informative and front-loaded, but there is clear redundancy: 'Use this after axint.upgrade or npm/pip upgrades' is echoed by 'Use: use after package upgrades so local project-pack hints stop naming old Axint versions.' Trimming this duplication would tighten the description.

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 full parameter schema, output schema, and annotations, the description covers the tool's purpose, usage timing, side effects, and dryRun behavior. The only notable gap is the minor parameter naming mismatch, which prevents a perfect score.

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?

The input schema provides complete descriptions for all four parameters, so the baseline is 3. The description adds high-level context about how cwd and targetVersion map to behavior, but it uses slightly inconsistent names (cwd vs targetDir, targetVersion vs version), which may confuse rather than clarify.

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 opens with a specific verb and resource: 'Update Axint-owned project-pack version hints after an upgrade.' It names concrete affected files and positions itself as a post-upgrade sync step, clearly distinguishing it from sibling tools like axint.upgrade.

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?

Explicit guidance is given: 'Use this after axint.upgrade or npm/pip upgrades.' The description repeats the invocation context in a 'Use:' clause, making it unmistakable when the tool should be applied.

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