Axint

axint.agent.install

Idempotent

Install the local Axint multi-agent project brain. Writes .axint/agent.json, .axint/context/latest.*, and .axint/coordination files so AI agents, Xcode, and humans coordinate through the same local truth layer. Use: use once per project to create local multi-agent coordination; not needed for one-off compile. Inputs: cwd scopes local coordination; projectName and hosts shape generated project-brain files. Effects: writes .axint/agent, context, and coordination files; no network.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "axint.agent.install"
  }
}

Input Schema

Name	Required	Description
`cwd`	No	Project directory. Defaults to the MCP process cwd.
`agent`	No	Active host/tool lane. Defaults to all.
`force`	No	Rewrite the existing local agent config if present.
`format`	No	Output format. Defaults to markdown.
`privacyMode`	No	Privacy posture for this project.
`projectName`	No	Optional project name override.
`providerMode`	No	Optional model-provider posture for future AI-enhanced advice. Defaults to none.

Output Schema

Name	Required	Description	Default
`text`	Yes
`isError`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedJul 16, 2026

changedInput schema / properties / privacyMode / description

Previous value: -"Privacy posture for this project. Defaults to local_only; source sharing is never enabled by default."New value: +"Privacy posture for this project."

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."

Changed4 schema fields changedMay 6, 2026

changedInput schema / properties / cwd / description

Previous value: -"Project directory. Defaults to the MCP..."New value: +"Project directory. Defaults to the MCP process cwd."

changedInput schema / properties / force / description

Previous value: -"Rewrite the existing local agent config if..."New value: +"Rewrite the existing local agent config if present."

changedInput schema / properties / privacyMode / description

Previous value: -"Privacy posture for this project. Defaults..."New value: +"Privacy posture for this project. Defaults to local_only; source sharing is never enabled by default."

changedInput schema / properties / providerMode / description

Previous value: -"Optional model-provider posture for future..."New value: +"Optional model-provider posture for future AI-enhanced advice. Defaults to none."

Changed8 schema fields changedMay 5, 2026

addedInput schema / properties / agent / description

Added value: +"Active host/tool lane. Defaults to all."

addedInput schema / properties / cwd / description

Added value: +"Project directory. Defaults to the MCP..."

addedInput schema / properties / force / description

Added value: +"Rewrite the existing local agent config if..."

addedInput schema / properties / format / description

Added value: +"Output format. Defaults to markdown."

addedInput schema / properties / privacyMode / description

Added value: +"Privacy posture for this project. Defaults..."

addedInput schema / properties / projectName / description
```
Added value: +"Optional project name override."
```

addedInput schema / properties / providerMode / description

Added value: +"Optional model-provider posture for future..."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "isError": {
+      "description": "Whether Axint marked the tool response as an error.",
+      "type": "boolean"
+    },
+    "text": {
+      "description": "Primary Axint tool response text, matching the first text content block.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text"
+  ],
+  "type": "object"
+}

AddedApr 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description discloses that it writes specific files (.axint/agent.json, context, coordination files) and that it makes no network calls. This adds meaningful detail beyond the annotations, which already indicate idempotentHint=true and destructiveHint=false. No contradiction.

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?

The description is organized with 'Use:', 'Inputs:', and 'Effects:' sections, making it scannable. It is slightly verbose but every sentence provides useful context (purpose, usage, effects). No wasted words.

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 presence of an output schema and annotations (idempotent, non-destructive), the description covers the essential context: what it does, when to use it, what files it writes, and that it's local-only. It doesn't explain return values, but the output schema handles that. Complete enough for a setup tool.

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 each parameter already has a clear description. The tool description adds some extra context (e.g., cwd scopes local coordination, projectName shapes files), but doesn't substantially improve on the schema's parameter docs. Baseline 3 applies.

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's purpose with a specific verb ('Install') and resource (local Axint multi-agent project brain). It distinguishes itself from siblings by noting it is a one-time per-project setup and explicitly says it's not needed for one-off compile, which differentiates it from tools like axint.compile.

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?

The description gives explicit usage guidance: 'use once per project to create local multi-agent coordination; not needed for one-off compile.' This clearly indicates when to use it and provides an exclusion. However, it doesn't mention alternative tools or when not to use it beyond compiling, so it's not 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 tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.