Skip to main content
Glama

axint.feature

Read-onlyIdempotent

Generate a complete Apple-native feature scaffold from a description: Swift source, view, Info.plist, entitlements, and XCTest files ready for direct placement into an Xcode project.

Instructions

Generate a scaffolded Apple-native feature package from a description. Returns multiple files: compile-aware Swift source, companion widget/view, Info.plist fragments, entitlements, and XCTest scaffolds — all structured file-by-file so an Xcode agent can write each file directly into the project. Designed for composition with Xcode MCP tools: call axint.feature to generate the package, then use XcodeWrite to place each file. Use: use for new Apple-native surfaces; not for repairing existing app bugs. Effects: read-only generated output; writes no files and uses no network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoPascalCase feature name, e.g., 'LogWaterIntake'.
domainNoApple App Intent domain.
formatNoWhen true (default), pipes every generated Swift file through swift-format with.
paramsNoExplicit parameter definitions as { fieldName: typeString }.
appNameNoThe target app name, used in generated comments and test references.
contextNoOptional nearby SwiftUI/design context.
platformNoTarget Apple platform for generated starter UI.
surfacesNoWhich Apple surfaces to generate. 'intent' produces an App Intent struct for.
descriptionYesWhat the feature does, in natural language. E.g., 'Let users log water intake via Siri' or 'Add a Spotlight-searchable recipe entity'.
componentKindNoOptional component blueprint for the component surface, such as feedCard.
tokenNamespaceNoOptional Swift token enum generated by axint.tokens.ingest, e.g., 'SwarmTokens'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
isErrorNo
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds explicit 'read-only generated output; writes no files and uses no network', reinforcing safety but not adding substantial new behavioral context.

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 structured sentences plus usage/effects labels. Front-loaded with purpose, no wasted words. Excellent conciseness.

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?

Given 11 parameters, output schema exists, and annotations provide safety hints, the description sufficiently covers purpose, usage, and behavior. No gaps for agent decision-making.

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 coverage is 100% with all parameters described. Description adds no parameter-level semantics beyond what's in the schema, so 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 generates a scaffolded Apple-native feature package from a description, listing specific files. It distinguishes from siblings like axint.scaffold by focusing on feature generation for new surfaces.

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 states use for new Apple-native surfaces, not for repairing bugs. Provides composition pattern with XcodeWrite. Clear when-to-use and alternatives.

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