Skip to main content
Glama

axint.xcode.write

Write a file inside an Axint-guarded Xcode project, automatically validate and cloud-check Swift files, then record guard artifacts.

Instructions

Write a file inside the Xcode project through the Axint guard path. For Swift files, runs axint.swift.validate and axint.cloud.check immediately, then records .axint/guard/latest.* proof. Use... Use: use only for guarded Xcode-project file writes; outside Xcode, patch normally and validate after. Effects: writes the requested file inside cwd, may create dirs, validates Swift, and may write guard/check artifacts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoProject root. Defaults to the MCP process cwd.
pathYesFile path to write. Relative paths are resolved inside cwd; absolute paths must still be inside cwd.
contentYesFull file contents to write.
projectNameNoProject name for guard/session reports.
expectedVersionNoExpected Axint version for this project.
platformNoTarget Apple platform for Cloud Check.
sessionTokenNoCurrent axint.session.start token, if already known.
createDirsNoWhether to create parent directories before writing. Defaults to true.
validateSwiftNoWhether to run Swift validation for .swift files. Defaults to true.
cloudCheckNoWhether to run Cloud Check for .swift files. Defaults to true.
notesNoAgent notes or user feedback to scan for drift while writing.
formatNoOutput format. Defaults to markdown.

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.
Behavior5/5

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

Annotations leave room for elaboration; the description adds that it writes files, may create directories, validates Swift, and produces guard/check artifacts. There is no contradiction with annotations.

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?

Two sentences plus separate 'Use:' and 'Effects:' sections provide all essential information without redundancy. Every sentence earns its place.

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?

For a tool with 12 parameters and an output schema, the description covers the core action, side effects, and usage boundary. It could detail parameter interactions slightly more, but overall it is sufficiently complete.

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?

Schema description coverage is 100%, so the baseline is 3. The description does not add parameter-level meaning beyond what the schema already provides for each of the 12 parameters.

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 writes a file inside an Xcode project via the Axint guard path, with specific details for Swift files. This uniquely identifies its purpose and distinguishes it from sibling tools like general file writing or project management.

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 instructions are given: 'use only for guarded Xcode-project file writes; outside Xcode, patch normally and validate after.' This provides clear when-to-use and when-not-to-use context.

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