Skip to main content
Glama

axint.scaffold

Read-onlyIdempotent

Generate a starter TypeScript intent file from a name and description. Returns a complete defineIntent() source string ready to save as a .ts file. No files written, no network requests.

Instructions

Generate a starter TypeScript intent file from a name and description. Returns a complete defineIntent() source string ready to save as a .ts file — no files are written, no network requests made. On invalid domain values, returns an error string. The output compiles directly with axint.compile. Use: use to create a small TypeScript intent starter; use templates.get for richer examples and compile for Swift output. Effects: read-only generated TypeScript; writes no files and uses no network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPascalCase intent name, e.g., 'SendMessage' or 'CreateEvent'. Must start with an uppercase letter and contain no spaces.
domainNoApple App Intent domain.
paramsNoInitial parameters for the intent.
descriptionYesHuman-readable description of what the intent does, shown to users in Shortcuts and Spotlight, e.g., 'Send a message to a contact'.

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, destructiveHint=false, idempotentHint=true. The description adds that no files are written, no network requests, and error handling for invalid domains, enhancing transparency 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 two sentences plus a concise usage directive. It is front-loaded with essential information and contains no unnecessary words.

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 the tool's low complexity (4 parameters, no nested objects, output schema implied), the description covers all key aspects: generation purpose, output format, side effects, error handling, and relation to other tools. It is complete.

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 context about invalid domain values and that name and description are key inputs, providing extra meaning beyond the schema.

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 starter TypeScript intent file, specifying verb, resource, and output format. It distinguishes from siblings like templates.get and compile, indicating unique functionality.

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 is provided: use for small starters, use templates.get for richer examples, and compile for Swift output. This clearly delineates when to use this tool versus 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