Skip to main content
Glama
agenticempire

axint

by agenticempire
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

axint.xcode.guard

Guards Xcode agent sessions against context compaction and Axint drift by checking project memory, active sessions, and freshness, ensuring proof before long tasks or edits.

Instructions

Guard an Xcode agent session against context compaction and Axint drift. Checks project memory files, active Axint session, latest Axint Run or guard proof, and long-task freshness. Use: call around long Xcode tasks, context recovery, broad Swift edits, or before claiming runtime proof; use workflow.check. Inputs: stage selects the gate; modifiedFiles and notes narrow drift checks; autoStartSession defaults true. Effects: writes .axint/guard proof and may start a session; does not edit app source or use network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoProject directory to guard. Defaults to the MCP process cwd.
notesNoAgent/user notes to scan for compaction, drift, forgotten Axint usage, or.
stageNoCurrent Xcode workflow stage. Defaults to context-recovery.
formatNoOutput format. Defaults to markdown.
platformNoTarget Apple platform, such as macOS, iOS, visionOS, or all.
projectNameNoProject name for the guard report.
writeReportNoWhether to write .axint/guard/latest.json and latest.md. Defaults to true.
sessionTokenNoCurrent axint.session.start token, if already known.
lastAxintToolNoLast Axint tool the agent used, e.g. axint.suggest or axint.feature.
modifiedFilesNoFiles in scope for this task.
expectedVersionNoExpected Axint version for the active project.
lastAxintResultNoShort result from the last Axint tool call.
autoStartSessionNoWhether to start axint.session.start automatically if no active session exists.
maxMinutesSinceAxintNoMaximum allowed minutes since latest Axint evidence. Defaults to 10.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
isErrorNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed15 schema fields changed
    • changedInput schema / properties / autoStartSession / description
      Previous value: -"Whether to start..."New value: +"Whether to start axint.session.start automatically if no active session exists."
    • changedInput schema / properties / cwd / description
      Previous value: -"Project directory..."New value: +"Project directory to guard. Defaults to the MCP process cwd."
    • changedInput schema / properties / expectedVersion / description
      Previous value: -"Expected Axint ve..."New value: +"Expected Axint version for the active project."
    • changedInput schema / properties / format / description
      Previous value: -"Output format. De..."New value: +"Output format. Defaults to markdown."
    • changedInput schema / properties / lastAxintResult / description
      Previous value: -"Short result from..."New value: +"Short result from the last Axint tool call."
    • changedInput schema / properties / lastAxintTool / description
      Previous value: -"Last Axint tool t..."New value: +"Last Axint tool the agent used, e.g. axint.suggest or axint.feature."
    • changedInput schema / properties / maxMinutesSinceAxint / description
      Previous value: -"Maximum allowed m..."New value: +"Maximum allowed minutes since latest Axint evidence. Defaults to 10."
    • changedInput schema / properties / modifiedFiles / description
      Previous value: -"Files in scope fo..."New value: +"Files in scope for this task."
    • addedInput schema / properties / modifiedFiles / items / description
      Added value: +"String value for this Axint parameter."
    • changedInput schema / properties / notes / description
      Previous value: -"Agent/user notes..."New value: +"Agent/user notes to scan for compaction, drift, forgotten Axint usage, or."
    • changedInput schema / properties / platform / description
      Previous value: -"Target Apple plat..."New value: +"Target Apple platform, such as macOS, iOS, visionOS, or all."
    • changedInput schema / properties / projectName / description
      Previous value: -"Project name for..."New value: +"Project name for the guard report."
    • changedInput schema / properties / sessionToken / description
      Previous value: -"Current axint.ses..."New value: +"Current axint.session.start token, if already known."
    • changedInput schema / properties / stage / description
      Previous value: -"Current Xcode wor..."New value: +"Current Xcode workflow stage. Defaults to context-recovery."
    • changedInput schema / properties / writeReport / description
      Previous value: -"Whether to write..."New value: +"Whether to write .axint/guard/latest.json and latest.md. Defaults to true."
  2. Changed17 schema fields changedv0.4.34
    • changedInput schema / properties / autoStartSession / description
      Previous value: -"Whether to start axint.session.start automatically if no active session exists. Defaults to true."New value: +"Whether to start..."
    • changedInput schema / properties / cwd / description
      Previous value: -"Project directory to guard. Defaults to the MCP process cwd."New value: +"Project directory..."
    • changedInput schema / properties / expectedVersion / description
      Previous value: -"Expected Axint version for the active project."New value: +"Expected Axint ve..."
    • changedInput schema / properties / format / description
      Previous value: -"Output format. Defaults to markdown."New value: +"Output format. De..."
    • changedInput schema / properties / lastAxintResult / description
      Previous value: -"Short result from the last Axint tool call."New value: +"Short result from..."
    • changedInput schema / properties / lastAxintTool / description
      Previous value: -"Last Axint tool the agent used, e.g. axint.suggest or axint.feature."New value: +"Last Axint tool t..."
    • changedInput schema / properties / maxMinutesSinceAxint / description
      Previous value: -"Maximum allowed minutes since latest Axint evidence. Defaults to 10."New value: +"Maximum allowed m..."
    • changedInput schema / properties / modifiedFiles / description
      Previous value: -"Files in scope for this task."New value: +"Files in scope fo..."
    • removedInput schema / properties / modifiedFiles / items / description
      Removed value: -"String value for this Axint parameter."
    • changedInput schema / properties / notes / description
      Previous value: -"Agent/user notes to scan for compaction, drift, forgotten Axint usage, or long-task risk."New value: +"Agent/user notes..."
    • changedInput schema / properties / platform / description
      Previous value: -"Target Apple platform, such as macOS, iOS, visionOS, or all."New value: +"Target Apple plat..."
    • changedInput schema / properties / projectName / description
      Previous value: -"Project name for the guard report."New value: +"Project name for..."
    • changedInput schema / properties / sessionToken / description
      Previous value: -"Current axint.session.start token, if already known."New value: +"Current axint.ses..."
    • changedInput schema / properties / stage / description
      Previous value: -"Current Xcode workflow stage. Defaults to context-recovery."New value: +"Current Xcode wor..."
    • changedInput schema / properties / writeReport / description
      Previous value: -"Whether to write .axint/guard/latest.json and latest.md. Defaults to 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."
  3. Changed9 schema fields changedv0.4.28
    • changedInput schema / properties / autoStartSession / description
      Previous value: -"Whether to start axint.session.start..."New value: +"Whether to start axint.session.start automatically if no active session exists. Defaults to true."
    • changedInput schema / properties / cwd / description
      Previous value: -"Project directory to guard. Defaults to the..."New value: +"Project directory to guard. Defaults to the MCP process cwd."
    • changedInput schema / properties / lastAxintTool / description
      Previous value: -"Last Axint tool the agent used, e.g...."New value: +"Last Axint tool the agent used, e.g. axint.suggest or axint.feature."
    • changedInput schema / properties / maxMinutesSinceAxint / description
      Previous value: -"Maximum allowed minutes since latest Axint..."New value: +"Maximum allowed minutes since latest Axint evidence. Defaults to 10."
    • changedInput schema / properties / notes / description
      Previous value: -"Agent/user notes to scan for compaction,..."New value: +"Agent/user notes to scan for compaction, drift, forgotten Axint usage, or long-task risk."
    • changedInput schema / properties / platform / description
      Previous value: -"Target Apple platform, such as macOS, iOS,..."New value: +"Target Apple platform, such as macOS, iOS, visionOS, or all."
    • changedInput schema / properties / sessionToken / description
      Previous value: -"Current axint.session.start token, if..."New value: +"Current axint.session.start token, if already known."
    • changedInput schema / properties / stage / description
      Previous value: -"Current Xcode workflow stage. Defaults to..."New value: +"Current Xcode workflow stage. Defaults to context-recovery."
    • changedInput schema / properties / writeReport / description
      Previous value: -"Whether to write .axint/guard/latest.json..."New value: +"Whether to write .axint/guard/latest.json and latest.md. Defaults to true."
  4. Addedv0.4.26

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations providing behavioral hints, the description effectively discloses key effects: writes .axint/guard proof, may start a session, and does not edit app source or use network. It could explicitly mention idempotency or safety, but the current disclosure is strong.

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

Conciseness5/5

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

The description is concise (three sentences) and well-structured: first sentence states purpose, second covers usage guidelines, third details effects and inputs. Every sentence provides essential information without redundancy.

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?

Given the tool's complexity (14 optional parameters, many siblings, output schema exists), the description covers all necessary aspects: purpose, when to use/alternatives, behavioral effects, and input hints. The output schema handles return value explanation, so nothing is missing.

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% with descriptions for each parameter. The tool description adds value by explaining the purpose of key parameters (e.g., 'stage selects the gate', 'modifiedFiles and notes narrow drift checks', 'autoStartSession defaults true'), enhancing understanding beyond the schema.

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 the tool guards against context compaction and Axint drift, specifying checks on project memory files, active session, and freshness. It distinguishes from sibling tools by explicitly mentioning 'use workflow.check' as an alternative for different needs.

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 description provides explicit usage context: 'call around long Xcode tasks, context recovery, broad Swift edits, or before claiming runtime proof'. It also advises when to use workflow.check instead, offering clear guidance on alternatives.

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