MakerPerks MCP-AQL Adapter
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp_aql_readA | Semantic READ endpoint for the MakerPerks builder-perks directory. Call with { operation: "introspect" } to discover the available operations (list_programs, get_program, search_programs) and their parameters, then call those. |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool, naming consistency is trivially maintained.
A single tool for a server that likely covers multiple operations feels too minimal; typically 3-15 tools are expected.
Only read operations are covered (via introspection and subsequent calls), with no support for create, update, or delete, which is a significant gap for a directory adapter.