Aicon
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 |
|---|---|
| loginC | Authenticate with your Icon MCP account through the web interface to access premium features. |
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 a single tool, there is no possibility of confusion between tools. The purpose of 'login' is clear and distinct within its narrow scope.
The single tool name 'login' is a clear, conventional verb that is easy to understand. There are no other tools to create inconsistencies or mixed naming conventions.
A single tool is too few for a server that promises 'premium features' and implies an underlying application surface. The server appears to offer authentication only, leaving core functionality unexposed.
The tool surface is severely incomplete. Only authentication is available; there are no tools to perform any actual premium functions, data operations, or other workflows that the login is meant to unlock.