Skip to main content
Glama
Sign In

Axint

by io.github.agenticempire
OverviewDiscussionsAdmin

axint.fix-packet

Read-onlyIdempotent

Read the latest Fix Packet that Axint emitted locally after a compile or watch run. Returns the exact repair artifact that AI tools or Xcode helpers should consume next: verdict, top findings, full diagnostics, next steps, and an AI-ready fix prompt. Use: use after a local compile/watch/check emitted a packet; not a new analysis pass. Inputs: cwd and path locate an existing packet; latest selects the newest artifact and never reruns analysis. Effects: read-only local artifact read; writes no files and uses 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.fix-packet"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoOptional working directory to search from.
formatNoOutput format. json returns the full packet, markdown returns the.
packetDirNoOptional explicit packet directory override.

Output Schema

NameRequiredDescriptionDefault
textYes
isErrorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / cwd / description
      Previous value: -"Optional working directory to search from. Axint walks upward from this directory until it finds..."New value: +"Optional working directory to search from."
    • changedInput schema / properties / format / description
      Previous value: -"Output format. json returns the full packet, markdown returns the human-readable report, and prompt returns..."New value: +"Output format. json returns the full packet, markdown returns the."
    • changedInput schema / properties / packetDir / description
      Previous value: -"Optional explicit packet directory override. Use this if the latest packet lives somewhere other than..."New value: +"Optional explicit packet directory override."
    • 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."
  2. Changed3 schema fields changed
    • changedInput schema / properties / cwd / description
      Previous value: -"Optional working directory to search from...."New value: +"Optional working directory to search from. Axint walks upward from this directory until it finds..."
    • changedInput schema / properties / format / description
      Previous value: -"Output format. json returns the full packet,..."New value: +"Output format. json returns the full packet, markdown returns the human-readable report, and prompt returns..."
    • changedInput schema / properties / packetDir / description
      Previous value: -"Optional explicit packet directory override...."New value: +"Optional explicit packet directory override. Use this if the latest packet lives somewhere other than..."
  3. Changed4 schema fields changed
    • addedInput schema / properties / cwd / description
      Added value: +"Optional working directory to search from...."
    • addedInput schema / properties / format / description
      Added value: +"Output format. json returns the full packet,..."
    • addedInput schema / properties / packetDir / description
      Added value: +"Optional explicit packet directory override...."
    • 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"
+}
  4. Changed3 schema fields changed
    • removedInput schema / properties / cwd / description
      Removed value: -"Optional working directory to search from. Axint walks upward from this directory until it finds .axint/fix/latest.json."
    • removedInput schema / properties / format / description
      Removed value: -"Output format. json returns the full packet, markdown returns the human-readable report, and prompt returns only the AI repair prompt."
    • removedInput schema / properties / packetDir / description
      Removed value: -"Optional explicit packet directory override. Use this if the latest packet lives somewhere other than .axint/fix."
  5. Added

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context beyond these: 'read-only local artifact read; writes no files and uses no network,' and 'never reruns analysis.' This clarifies side effects and network usage, which are not fully covered by the annotations, making the description more informative. No contradictions found.

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 compact and well-structured. It opens with the core action, lists return contents, then gives usage context, inputs, and effects in a logical order. Every sentence adds meaningful information, with no fluff or redundancy. The 'Use:' and 'Inputs:' labels help parsing, and the length is appropriate for the tool's complexity.

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?

The tool is relatively simple (read-only artifact retrieval) and the description covers purpose, usage, return content, and side effects. The presence of an output schema reduces the need to describe return format in detail. Minor gaps include a truncated schema description for 'format' and the 'path' vs 'packetDir' wording, but these do not materially impede understanding for an agent.

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?

All three parameters (cwd, format, packetDir) are described in the input schema (100% coverage). The description adds context that cwd and packetDir locate an existing packet, but it mentions 'path' instead of 'packetDir,' causing slight ambiguity. The 'latest' behavior is described but is not tied to a specific parameter, which could confuse an agent. Overall, the schema already carries the semantic load, and the description provides marginal additional value.

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 what the tool does: reads the latest Fix Packet emitted by Axint after a compile or watch run. It specifies the exact contents returned (verdict, findings, diagnostics, next steps, fix prompt) and explicitly distinguishes itself from a new analysis pass. This is a specific verb+resource combination that differentiates it from sibling tools like axint.compile or axint.repair.

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 when-to-use guidance: 'use after a local compile/watch/check emitted a packet; not a new analysis pass.' This tells the agent when to invoke it and implicitly when not to, but it does not name alternative sibling tools. Providing an explicit exclusion without naming alternatives is slightly below the highest bar.

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

All Axint toolsInspect
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.

Resources