Skip to main content
Glama

axint.compile

Read-onlyIdempotent

Compile TypeScript source with defineIntent() into native Swift App Intent code. Returns generated Swift and optional Info.plist or entitlements as a string without writing files or network requests.

Instructions

Compile TypeScript source (defineIntent() call) into native Swift App Intent code. Returns { swift, infoPlist?, entitlements? } as a string — no files written, no network requests. On validation failure, returns diagnostics... Use: use when TypeScript DSL source should become Swift; use validate for cheaper preflight only. Effects: read-only generated Swift/diagnostics; writes no files and uses no network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYesFull TypeScript source code containing a defineIntent() call. Must be a complete file starting with an axint...
fileNameNoOptional file name used in diagnostic messages, e.g., 'SendMessage.intent.ts'. Defaults to 'input.ts' if...
emitInfoPlistNoWhen true, returns an Info.plist XML fragment declaring the intent's infoPlistKeys. Only relevant for...
emitEntitlementsNoWhen true, returns an .entitlements XML fragment for the intent's declared entitlements. Only relevant for...
formatNoWhen true (default), pipes generated Swift through swift-format with Axint's house style. Falls back to raw...

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.
Behavior4/5

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

Description adds return structure and side-effect details (no files/network) beyond annotations, but annotations already cover read-only and idempotent nature.

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?

Concise, front-loaded with main purpose, each sentence adds value without unnecessary detail.

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?

Covers purpose, usage, effects, and return structure; adequate given rich annotations and output schema, though no edge-case handling mentioned.

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?

With 100% schema coverage, description adds value by explaining how emitInfoPlist/emitEntitlements map to return fields and format behavior.

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?

Clearly states it compiles TypeScript defineIntent() into native Swift App Intent code, distinguishing it from validate and sibling tools.

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 says when to use (compile) and when to use validate as a cheaper alternative, providing clear usage context.

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