Skip to main content
Glama

axint.suggest

Read-onlyIdempotent

Suggests Apple-native features and surfaces for an app based on its description. Returns a ranked list with recommended intents, widgets, or views to guide surface selection before generation.

Instructions

Suggest Apple-native features for an app based on its description. The domain is only a weak hint; the app description wins. Returns a ranked list of features with recommended surfaces (intent, widget, view,... Use: use before generation to choose Apple surfaces; not a substitute for registry search or validation. Effects: local mode is read-only; Pro mode may call Axint endpoint when credentials are configured.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appDescriptionYesWhat the app does, in natural language. E.g., 'A fitness tracking app that logs workouts and counts steps'...
domainNoPrimary app domain. One of: messaging, productivity, health, social, community, collaboration,...
modeNoSuggestion strategy. local is deterministic and offline. pro/ai uses the authenticated Axint Pro...
platformNoOptional Apple platform target used by AI mode to tailor suggestions.
audienceNoOptional audience context, such as consumers, teams, operators, developers, clinicians, creators, or...
excludeNoOptional concepts to avoid, for example ['dating', 'fitness'].
goalsNoOptional product goals for Pro mode, such as activation, retention, conversion, speed, accessibility, or...
stageNoOptional product stage used by Pro mode to tune suggestions without embedding private strategy logic in the...
constraintsNoOptional constraints for Pro mode, such as must be macOS-native, no server, no payments, or build in one...
limitNoMaximum number of suggestions to return. Defaults to 5. Suggestions are ordered by estimated user impact.

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

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

Annotations already declare readOnlyHint=true; description adds context that local mode is read-only and Pro mode may call an endpoint. It also explains return type (ranked list) and mode effects, adding 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: purpose, usage guidance, effects. Front-loaded with main verb-resource. No filler, every sentence adds value.

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 complexity (10 params, 1 required, output schema exists), the description covers purpose, usage, param hints, mode effects, and return type. Output schema exists so return details are not needed. Complete for an AI agent.

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. Description adds value by clarifying that 'domain is only a weak hint; the app description wins', which gives semantics to the domain parameter. Also mentions mode effects connecting to parameters.

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 'Suggest Apple-native features for an app based on its description' with a specific verb and resource. It distinguishes from siblings by explicitly saying 'not a substitute for registry search or validation'.

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?

Provides explicit when-to-use guidance: 'use before generation to choose Apple surfaces'. Also tells when not to use: 'not a substitute for registry search or validation'. Mentions mode-specific behavior.

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