Skip to main content
Glama

axint.feedback.create

Create a redacted feedback packet to document weak Axint repair output. Includes diagnostic codes, issue class, and evidence without source code.

Instructions

Create or read a privacy-safe learning packet for Axint repair intelligence. Packets include project shape, diagnostic codes, issue class, redacted evidence, and likely product owner, but never include source code. Users... Use: use when Axint output was weak and you need a privacy-safe issue packet; not for sending source. Effects: writes or reads redacted .axint/feedback packets; never includes source by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoProject directory. Defaults to the MCP process cwd.
latestNoWhen true, return the latest local feedback packet instead of creating a new one.
issueNoBug, weak Axint output, or failed repair behavior.
sourceNoOptional inline Swift source used locally only.
sourcePathNoOptional suspected Swift file path used locally only.
fileNameNoDisplay file name when passing inline source.
platformNoTarget Apple platform hint.
agentNoActive host/tool lane.
expectedBehaviorNoOptional expected behavior.
actualBehaviorNoOptional actual behavior.
xcodeBuildLogNoOptional Xcode build/test log evidence.
testFailureNoOptional focused unit/UI-test failure text.
runtimeFailureNoOptional crash, freeze, hang, or runtime failure text.
changedFilesNoChanged files to pin into the context pack.
projectContextPathNoOptional .axint/context/latest.json path.
formatNoOutput format. Defaults to json.

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 show readOnlyHint=false, consistent with the description saying it can create or read. The description adds that packets are redacted and never include source code, providing full behavioral insight 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?

The description is three sentences, front-loaded with purpose, then usage, then 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.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 16 optional parameters with schema descriptions and an output schema, the description adequately covers the tool's purpose, usage, and constraints. The only gap is no explicit mention of return value format, but output schema exists.

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?

Input schema has 100% coverage with descriptions for all 16 parameters. The description adds high-level context about packet contents but does not detail individual parameters beyond schema, so a baseline of 3 is appropriate.

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 creates or reads a privacy-safe learning packet for Axint repair intelligence. It specifies the resource type and distinguishes from siblings like axint.fix-packet by focusing on feedback packets.

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 usage guidance is provided: 'Use when Axint output was weak and you need a privacy-safe issue packet; not for sending source.' Also outlines effects, making it clear when to use this tool.

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