AI Tools MCP
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_toolsA | Returns all AI tool cards from the database. Each card includes the tool name, description, pricing, platform, what it does, and when to use it. Sourced from The AI Search YouTube channel. Tip: call this from a sub-agent to keep the main thread's context clean. |
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
With only one tool exposed, there is no possibility of confusion or overlap. The tool's purpose is singular and unambiguous.
The single tool name follows a clear verb_noun snake_case convention. With only one tool, there is no inconsistent pattern to penalize.
A one-tool server feels too thin for the broad 'AI Tools MCP' scope. Even if the single function is useful, agents have no complementary operations or filtering capabilities.
The tool only returns all AI tool cards at once, with no filtering, searching, retrieval by ID, or management operations. Significant gaps exist for a server ostensibly about AI tools.