Skip to main content
Glama

axint.scaffold

Read-onlyIdempotent

Generate a TypeScript intent starter from a name and description. Returns a ready-to-save defineIntent() string with no file writes or 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. Inputs: name must be PascalCase; params define the starter contract; domain defaults to general. 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
Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds specific behaviors: no files written, no network requests, returns error string on invalid domain values, and output compiles with axint.compile. No contradictions.

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 a single dense paragraph that front-loads the main action. It is concise but could be slightly more structured (e.g., bullet points for use cases). Still, every sentence serves a purpose and no fluff.

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 simplicity and the presence of an output schema (implied), the description covers return type, behavior, error handling, and relationships to sibling tools. It provides enough context for an agent to use it correctly.

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%, so baseline is 3. The description adds extra guidance: 'name must be PascalCase', 'params define the starter contract', and 'domain defaults to general', which improves usability beyond schema descriptions.

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 'generate a starter TypeScript intent file' and returns a source string, distinguishing it from siblings like 'axint.compile' and 'axint.templates.get' by noting alternatives for richer examples or Swift output.

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 'use to create a small TypeScript intent starter' and contrasts with 'templates.get for richer examples and compile for Swift output', giving clear when-to-use and when-not-to-use guidance.

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