Skip to main content
Glama

axint.agent.install

Idempotent

Installs local multi-agent coordination files so AI agents, Xcode, and humans share the same project truth layer. Use once per project to set up .axint/agent, context, and coordination files.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoProject directory. Defaults to the MCP process cwd.
agentNoActive host/tool lane. Defaults to all.
forceNoRewrite the existing local agent config if present.
formatNoOutput format. Defaults to markdown.
privacyModeNoPrivacy posture for this project.
projectNameNoOptional project name override.
providerModeNoOptional model-provider posture for future AI-enhanced advice. Defaults to none.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
isErrorNo

Schema Changelog

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

  1. Changed7 schema fields changed
    • changedInput schema / properties / agent / description
      Previous value: -"Active host/tool..."New value: +"Active host/tool lane. Defaults to all."
    • changedInput schema / properties / cwd / description
      Previous value: -"Project directory..."New value: +"Project directory. Defaults to the MCP process cwd."
    • changedInput schema / properties / force / description
      Previous value: -"Rewrite the exist..."New value: +"Rewrite the existing local agent config if present."
    • changedInput schema / properties / format / description
      Previous value: -"Output format. De..."New value: +"Output format. Defaults to markdown."
    • changedInput schema / properties / privacyMode / description
      Previous value: -"Privacy posture f..."New value: +"Privacy posture for this project."
    • changedInput schema / properties / projectName / description
      Previous value: -"Optional project..."New value: +"Optional project name override."
    • changedInput schema / properties / providerMode / description
      Previous value: -"Optional model-pr..."New value: +"Optional model-provider posture for future AI-enhanced advice. Defaults to none."
  2. Changed9 schema fields changedv0.4.34
    • changedInput schema / properties / agent / description
      Previous value: -"Active host/tool lane. Defaults to all."New value: +"Active host/tool..."
    • changedInput schema / properties / cwd / description
      Previous value: -"Project directory. Defaults to the MCP process cwd."New value: +"Project directory..."
    • changedInput schema / properties / force / description
      Previous value: -"Rewrite the existing local agent config if present."New value: +"Rewrite the exist..."
    • changedInput schema / properties / format / description
      Previous value: -"Output format. Defaults to markdown."New value: +"Output format. De..."
    • 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 f..."
    • changedInput schema / properties / projectName / description
      Previous value: -"Optional project name override."New value: +"Optional project..."
    • changedInput schema / properties / providerMode / description
      Previous value: -"Optional model-provider posture for future AI-enhanced advice. Defaults to none."New value: +"Optional model-pr..."
    • 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. Changed4 schema fields changedv0.4.28
    • 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."
  4. Addedv0.4.26

TDQS

A4.9/5.0
Behavior5/5

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

Description details effects: 'writes .axint/agent, context, and coordination files; no network', which aligns with annotations (idempotentHint=true, destructiveHint=false). Adds behavioral context beyond 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?

Three concise sentences front-loading the core purpose, usage, and effects. No wasted words; every sentence adds value.

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?

Covers purpose, usage, effects, and parameter roles. With an output schema present, no need to detail return values. Complete for an installer tool.

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 has 100% parameter descriptions, but description adds functional context like 'cwd scopes local coordination' and 'projectName and hosts shape generated project-brain files', providing meaning beyond 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 'Install the local Axint multi-agent project brain' with specific verb and resource. It lists the files written, distinguishing it from sibling tools like axint.compile by noting 'not needed for one-off compile'.

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?

Explicitly says 'use once per project to create local multi-agent coordination; not needed for one-off compile', providing clear when-to-use and when-to-avoid guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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