Skip to main content
Glama
agenticempire

axint

by agenticempire
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Hybrid

axint.feature

Read-onlyIdempotent

Generate a scaffolded Apple-native feature package from a description. Returns Swift source, widget/view, Info.plist, entitlements, and XCTest scaffolds structured for direct Xcode integration.

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. Use: use for new Apple-native surfaces; not for repairing existing app bugs. Inputs: description is the feature brief; kind and platform constrain the generated package. 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • changedInput schema / properties / appName / description
      Previous value: -"The target app na..."New value: +"The target app name, used in generated comments and test references."
    • changedInput schema / properties / componentKind / description
      Previous value: -"Optional componen..."New value: +"Optional component blueprint for the component surface, such as feedCard."
    • changedInput schema / properties / context / description
      Previous value: -"Optional nearby S..."New value: +"Optional nearby SwiftUI/design context."
    • changedInput schema / properties / description / description
      Previous value: -"What the feature does, in natural language. E.g., 'Let users..."New value: +"What the feature does, in natural language. E.g., 'Let users log water intake via Siri' or 'Add a Spotlight-searchable recipe entity'."
    • changedInput schema / properties / domain / description
      Previous value: -"Apple App Intent..."New value: +"Apple App Intent domain."
    • changedInput schema / properties / format / description
      Previous value: -"When true (defaul..."New value: +"When true (default), pipes every generated Swift file through swift-format with."
    • changedInput schema / properties / name / description
      Previous value: -"PascalCase featur..."New value: +"PascalCase feature name, e.g., 'LogWaterIntake'."
    • addedInput schema / properties / params / additionalProperties / description
      Added value: +"Swift type for this parameter."
    • changedInput schema / properties / params / description
      Previous value: -"Explicit paramete..."New value: +"Explicit parameter definitions as { fieldName: typeString }."
    • changedInput schema / properties / platform / description
      Previous value: -"Target Apple plat..."New value: +"Target Apple platform for generated starter UI."
    • changedInput schema / properties / surfaces / description
      Previous value: -"Which Apple surfa..."New value: +"Which Apple surfaces to generate. 'intent' produces an App Intent struct for."
    • addedInput schema / properties / surfaces / items / description
      Added value: +"Allowed string value for this Axint parameter."
    • changedInput schema / properties / tokenNamespace / description
      Previous value: -"Optional Swift to..."New value: +"Optional Swift token enum generated by axint.tokens.ingest, e.g., 'SwarmTokens'."
  2. Changed15 schema fields changedv0.4.34
    • changedInput schema / properties / appName / description
      Previous value: -"The target app name, used in generated comments and test references. E.g., 'HealthTracker'. Optional."New value: +"The target app na..."
    • changedInput schema / properties / componentKind / description
      Previous value: -"Optional component blueprint for the component surface, such as feedCard, mediaCard, utilityRow, avatar,..."New value: +"Optional componen..."
    • changedInput schema / properties / context / description
      Previous value: -"Optional nearby SwiftUI/design context. Axint uses this as a weak hint for layout primitives, platform..."New value: +"Optional nearby S..."
    • changedInput schema / properties / description / description
      Previous value: -"What the feature does, in natural language. E.g., 'Let users log water intake via Siri' or 'Add a..."New value: +"What the feature does, in natural language. E.g., 'Let users..."
    • changedInput schema / properties / domain / description
      Previous value: -"Apple App Intent domain. One of: messaging, productivity, health, social, community, collaboration,..."New value: +"Apple App Intent..."
    • changedInput schema / properties / format / description
      Previous value: -"When true (default), pipes every generated Swift file through swift-format with Axint's house style. Falls..."New value: +"When true (defaul..."
    • changedInput schema / properties / name / description
      Previous value: -"PascalCase feature name, e.g., 'LogWaterIntake'. If omitted, inferred from the description. Used as the base..."New value: +"PascalCase featur..."
    • removedInput schema / properties / params / additionalProperties / description
      Removed value: -"Swift type for this parameter"
    • changedInput schema / properties / params / description
      Previous value: -"Explicit parameter definitions as { fieldName: typeString }. E.g., { amount: 'double', unit: 'string' }. If..."New value: +"Explicit paramete..."
    • changedInput schema / properties / platform / description
      Previous value: -"Target Apple platform for generated starter UI. Use 'macOS' to avoid iOS-only SwiftUI affordances in..."New value: +"Target Apple plat..."
    • changedInput schema / properties / surfaces / description
      Previous value: -"Which Apple surfaces to generate. 'intent' produces an App Intent struct for Siri/Shortcuts/Spotlight...."New value: +"Which Apple surfa..."
    • removedInput schema / properties / surfaces / items / description
      Removed value: -"Allowed string value for this Axint parameter."
    • changedInput schema / properties / tokenNamespace / description
      Previous value: -"Optional Swift token enum generated by axint.tokens.ingest, e.g., 'SwarmTokens'. When provided, generated..."New value: +"Optional Swift to..."
    • 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. Changed1 schema field changed
    • changedInput schema / properties / surfaces / items / enum
      Previous value: -[
-  "intent",
-  "view",
-  "widget",
-  "component",
-  "app",
-  "store"
-]New value: +[
+  "intent",
+  "view",
+  "widget",
+  "component",
+  "app",
+  "store",
+  "model",
+  "models",
+  "state",
+  "data"
+]
  4. Changed11 schema fields changedv0.4.28
    • changedInput schema / properties / appName / description
      Previous value: -"The target app name, used in generated..."New value: +"The target app name, used in generated comments and test references. E.g., 'HealthTracker'. Optional."
    • changedInput schema / properties / componentKind / description
      Previous value: -"Optional component blueprint for the..."New value: +"Optional component blueprint for the component surface, such as feedCard, mediaCard, utilityRow, avatar,..."
    • changedInput schema / properties / context / description
      Previous value: -"Optional nearby SwiftUI/design context...."New value: +"Optional nearby SwiftUI/design context. Axint uses this as a weak hint for layout primitives, platform..."
    • changedInput schema / properties / description / description
      Previous value: -"What the feature does, in natural language...."New value: +"What the feature does, in natural language. E.g., 'Let users log water intake via Siri' or 'Add a..."
    • changedInput schema / properties / domain / description
      Previous value: -"Apple App Intent domain. One of: messaging,..."New value: +"Apple App Intent domain. One of: messaging, productivity, health, social, community, collaboration,..."
    • changedInput schema / properties / format / description
      Previous value: -"When true (default), pipes every generated..."New value: +"When true (default), pipes every generated Swift file through swift-format with Axint's house style. Falls..."
    • changedInput schema / properties / name / description
      Previous value: -"PascalCase feature name, e.g., 'LogWaterIntak..."New value: +"PascalCase feature name, e.g., 'LogWaterIntake'. If omitted, inferred from the description. Used as the base..."
    • changedInput schema / properties / params / description
      Previous value: -"Explicit parameter definitions as {..."New value: +"Explicit parameter definitions as { fieldName: typeString }. E.g., { amount: 'double', unit: 'string' }. If..."
    • changedInput schema / properties / platform / description
      Previous value: -"Target Apple platform for generated starter..."New value: +"Target Apple platform for generated starter UI. Use 'macOS' to avoid iOS-only SwiftUI affordances in..."
    • changedInput schema / properties / surfaces / description
      Previous value: -"Which Apple surfaces to generate. 'intent'..."New value: +"Which Apple surfaces to generate. 'intent' produces an App Intent struct for Siri/Shortcuts/Spotlight...."
    • changedInput schema / properties / tokenNamespace / description
      Previous value: -"Optional Swift token enum generated by..."New value: +"Optional Swift token enum generated by axint.tokens.ingest, e.g., 'SwarmTokens'. When provided, generated..."
  5. Addedv0.4.26

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description goes further by stating 'writes no files and uses no network' and 'read-only generated output.' It also discloses that output is structured file-by-file for an Xcode agent to write. This adds meaningful behavior beyond the annotations, though the idempotentHint is not explicitly reinforced.

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 well-structured with clear sections: main action, return value, usage, inputs, and effects. Each sentence provides distinct information, and the most critical fact (what the tool does) is front-loaded. Minor redundancy in 'read-only generated output' and 'writes no files' could be trimmed, but overall it is efficient.

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?

For a tool with 11 parameters, nested objects, and an output schema, the description offers a good high-level context: it clarifies the use case, output structure, and side-effect profile. The only notable gap is the misleading 'kind' reference and the lack of explicit mention of the output schema (though the schema itself is present). Given the schema's richness, the description suffices for guiding invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds a helpful note that 'description' is the feature brief and that 'platform' constrains the package. However, it also mentions 'kind' as an input, yet no parameter named 'kind' exists in the schema—this is misleading. The ambiguity undermines the added value and could lead an agent to look for a non-existent parameter.

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 opens with a specific verb+noun: 'Generate a scaffolded Apple-native feature package from a description.' It then enumerates the output file types, making the tool's purpose unmistakable. The 'Use' clause also distinguishes it from repair tools, and the name 'feature' aligns with new-surface generation.

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 explicitly states when to use it ('for new Apple-native surfaces') and when not to ('not for repairing existing app bugs'). However, it does not name a specific alternative tool (e.g., axint.repair or axint.scaffold), so the guidance is clear but lacks a direct pointer to the sibling.

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