context-awesome
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONTEXT_AWESOME_API_HOST | No | Backend API host | https://api.context-awesome.com |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_awesome_sectionA | Discovers sections/categories across awesome lists matching a search query and returns matching sections from awesome lists. You MUST call this function before 'get_awesome_items' to discover available sections UNLESS the user explicitly provides a githubRepo or listId. Selection Process:
Response Format:
For ambiguous queries, multiple relevant sections will be returned for the user to choose from. |
| get_awesome_itemsA | Retrieves items from a specific awesome list or section with token limiting. You must call 'find_awesome_section' first to discover available sections, UNLESS the user explicitly provides a githubRepo or listId. |
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 2 tools
The two tools have clearly distinct purposes: 'find_awesome_section' discovers sections/categories across awesome lists based on a search query, while 'get_awesome_items' retrieves actual items from a specific list or section. There is no overlap in functionality—one is for discovery and the other for retrieval, making them perfectly distinguishable.
Both tools follow a consistent verb_noun pattern with snake_case: 'find_awesome_section' and 'get_awesome_items'. The naming is predictable and readable, with 'find' and 'get' as appropriate verbs for their respective actions, maintaining uniformity throughout the set.
With only 2 tools, the server feels thin for its apparent purpose of interacting with awesome lists. While the tools cover discovery and retrieval, typical operations like creating, updating, or deleting items are missing, suggesting the scope might be limited or incomplete. A count of 2 is borderline for a functional server in this domain.
The tool surface is significantly incomplete for the domain of awesome list management. It only supports discovery and retrieval, lacking any CRUD operations such as adding, updating, or removing items or sections. This will likely cause agent failures when full lifecycle management is needed, as there are obvious gaps in coverage.