sourcesage
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| register_entityB | Register a code entity in the knowledge graph. Args: name: Name of the entity (e.g., class name, function name) entity_type: Type of entity (class, function, module, etc.) summary: Brief description of the entity signature: Entity signature (e.g., function signature) language: Programming language observations: List of observations about the entity metadata: Additional metadata as key-value pairs |
| register_relationshipC | Register a relationship between entities. Args: from_entity: Name of the source entity to_entity: Name of the target entity relationship_type: Type of relationship (calls, inherits, imports, etc.) metadata: Additional metadata as key-value pairs |
| register_patternB | Register a code pattern. Args: name: Name of the pattern description: Description of the pattern language: Programming language example: Example code demonstrating the pattern metadata: Additional metadata as key-value pairs |
| register_style_conventionC | Register a coding style convention. Args: name: Name of the convention description: Description of the convention language: Programming language examples: Example code snippets demonstrating the convention metadata: Additional metadata as key-value pairs |
| add_entity_observationC | Add an observation to an entity. Args: entity_name: Name of the entity observation: Observation to add |
| query_entitiesB | Query entities in the knowledge graph. Args: entity_type: Filter by entity type (class, function, module, etc.) language: Filter by programming language name_pattern: Filter by name pattern (regex) limit: Maximum number of results to return |
| get_entity_detailsC | Get detailed information about an entity. Args: entity_name: Name of the entity |
| query_patternsB | Query code patterns in the knowledge graph. Args: language: Filter by programming language pattern_name: Filter by pattern name |
| query_style_conventionsA | Query coding style conventions in the knowledge graph. Args: language: Filter by programming language convention_name: Filter by convention name |
| get_knowledge_statisticsC | Get statistics about the knowledge graph. |
| clear_knowledgeA | Clear all knowledge from the graph. |
| load_project_understandingB | Load understanding of an entire project at once. This tool should be used by MCP clients to quickly get project understanding if available, instead of reading all the files individually. It loads all entities, relationships, patterns, and style conventions related to the project. Args: project_path: Path to the project root directory |
| dump_project_understandingA | Dump understanding of an entire project at once. This tool provides a comprehensive dump of all knowledge related to a project, including all entities, relationships, patterns, and style conventions. Args: project_path: Path to the project root directory include_observations: Whether to include detailed observations |
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 13 tools
Each tool has a clearly distinct purpose. Query, register, and utility tools are well-separated; even similar verbs like 'dump' and 'load' target different operations (output vs input). No overlapping functionality.
All tool names follow a consistent verb_noun pattern using snake_case. Verbs like register, query, get, add, clear, dump, load are distinct and predictable. Nouns clearly indicate the resource.
13 tools is well within the ideal range for a domain-specific knowledge graph server. The number covers core operations without being excessive, and each tool serves a specific purpose.
Missing update and delete operations for entities, patterns, relationships, and style conventions. Also lacks a dedicated query for relationships and a way to list all entities without filtering. These gaps can cause agent failures when needing to modify or remove specific data.