AAJ Marketing Engines
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_enginesA | Lists every AAJ marketing engine: its id, the question it answers, and its category. Engines cover unit economics, pipeline forecast, budget allocation, retention, A/B significance, SEO/GEO scoring, ad spend and pricing. |
| describe_engineA | Shows one engine's input schema: required fields, units, alternative shapes, and a worked example. Engines reject bad input rather than guessing. |
| run_engineA | Runs an AAJ engine and returns its verdict. Give |
| search_skillsA | Finds AAJ marketing skills by the problem they solve — 'churn is rising', 'we're launching next month', 'not showing up in AI answers'. Returns matching methods and marks which have a runnable engine. |
| get_skillA | Returns the full method for one skill: when to use it, the steps, the quality bar, and how to run its engine if it has one. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct role: list/search for discovery, get_skill/describe_engine for detail, run_engine for execution. The only mild friction is the two overlapping entity layers (skills vs. engines) — get_skill mentions running an engine while describe_engine shows the engine schema — but the verb distinguishes intent clearly enough.
All five tools follow a strict verb_noun snake_case pattern (run_engine, search_skills, get_skill, list_engines, describe_engine). The convention is applied uniformly with no deviations in casing or style.
Five tools is well-scoped for a server exposing two related entity types: discovery (list_engines, search_skills), detail (get_skill, describe_engine), and execution (run_engine). No tool feels redundant, and none is missing at this granularity.
The lifecycle is largely covered: find skills, inspect a skill, list/describe/run engines. Minor gaps exist — no plain 'list all skills' without a problem query, and no batch or multi-engine run — but these are workable around since skills are discoverable via search_skills.