DevBrain
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| retrieve_knowledgeA | Queries DevBrain (aka Args:
query: The question or ask to query for knowledge.
tags: Optional comma-separated list of tags (keywords) to filter or ground the search. (e.g.: Returns: str: Helpful knowledge and context information from DevBrain (articles include title, short description and a URL to the full article to read it later). |
| read_full_articleC | Returns the full content of an article identified by its URL. Args: url: The URL of the article to read. Returns: str: The full content of the article or an error message. |
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 completely distinct purposes: one fetches full article content from a specific URL, while the other queries a knowledge base with a search query and optional tags. There is no functional overlap or ambiguity between these operations.
Both tools follow a clear verb_noun pattern (read_full_article, retrieve_knowledge) with consistent snake_case formatting. The naming conventions are predictable and semantically appropriate for their functions.
With only 2 tools, the server feels severely under-scoped for a system described as a 'developer's brain' knowledge base. A comprehensive knowledge system would typically need more operations like searching, filtering, listing, or managing knowledge entries beyond just retrieving content and querying.
The tool surface is incomplete for a knowledge base system. While it provides retrieval of specific articles and knowledge queries, it lacks essential operations like listing available articles, searching by metadata, updating knowledge, or managing the knowledge base structure. This creates significant gaps for agent workflows.