Skip to main content
Glama

axint.schema.compile

Read-onlyIdempotent

Compile minimal JSON schema to Swift, bypassing TypeScript DSL. Supports intents, views, components, widgets, and full apps with low token usage.

Instructions

Compile a minimal JSON schema directly to Swift, bypassing the TypeScript DSL entirely. Supports intents, views, components, widgets, and full apps via the 'type' parameter. Uses ~20 input tokens vs hundreds for TypeScript — ideal for LLM agents optimizing token budgets. Use: use for token-light JSON-to-Swift generation; use compile for full TypeScript DSL control and scaffold for TS starters. Inputs: schema kind selects intent, view, widget, or app output; options add companion metadata. Effects: read-only Swift generation; writes no files and uses no network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoView/widget only.
nameYesPascalCase name, e.g., 'CreateEvent' for intents, 'EventListView' for views, 'StepsWidget' for widgets. Used as the Swift struct name.
typeYesWhat to compile.
entryNoWidget only. Timeline entry fields as { fieldName: typeString }.
propsNoView only. Prop definitions as { fieldName: typeString }.
stateNoView only.
titleNoHuman-readable title shown in Shortcuts/Spotlight. Intent only.
domainNoApple App Intent domain. Intent only.
formatNoWhen true (default), pipes generated Swift through swift-format with Axint's.
paramsNoIntent only. Parameter definitions as { fieldName: typeString }.
scenesNoApp only. Scene definitions for the @main App struct.
familiesNoWidget only.
platformNoOptional target Apple platform hint for view/widget generation.
descriptionNoDescription of what this intent/view/widget does.
displayNameNoWidget only. Human-readable name shown in the widget gallery.
componentKindNoComponent only. Optional known component shape.
tokenNamespaceNoOptional Swift token enum generated by axint.tokens.ingest, e.g., 'SwarmTokens'.
refreshIntervalNoWidget only. Timeline refresh interval in minutes.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
isErrorNo
Behavior4/5

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

Description states 'read-only Swift generation; writes no files and uses no network,' which aligns with annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false). Adds context on safety and side effects 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 sentences: main action, capabilities, usage. No wasted words; front-loaded with key information.

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, alternatives, token efficiency, and side effects. With a rich schema and output schema present, the description provides sufficient context for correct tool selection.

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 coverage is 100% with detailed parameter descriptions. The description adds token-budget context and clarifies parameter roles (e.g., 'body: View/widget only'), but the schema already provides comprehensive definitions.

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 compiles a minimal JSON schema to Swift, bypassing TypeScript DSL. It specifies supported outputs (intents, views, components, widgets, apps) via the 'type' parameter, and distinguishes from sibling tools like axint.compile and axint.scaffold by naming them directly.

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 guidance: 'use for token-light JSON-to-Swift generation; use compile for full TypeScript DSL control and scaffold for TS starters.' This tells the agent when to choose this tool over 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