Bob Demo MCP Server
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
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 9 tools
Tools have distinct names covering different aspects (analysis, navigation, file operations), but lack descriptions could cause some ambiguity between similar-sounding tools like analyze_code_complexity and analyze_project_structure.
All tools follow a consistent verb_noun pattern with snake_case (e.g., analyze_code_complexity, get_repository_info, list_directory). No mixed conventions.
9 tools is well-scoped for a code analysis server, covering analysis, navigation, file reading, and searching without being overwhelming.
The set covers common code analysis tasks (complexity, history, structure, definitions, diff, file operations). Minor gaps like missing metadata or branch comparison, but overall sufficient for the inferred domain.