context-bridge
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 |
|---|---|
| list_documentsC | List supported documents in a directory |
| read_documentB | Extract text from a file |
| search_documentsC | Search text within documents |
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 3 tools
Each tool has a unique function: listing available documents, reading document content, and searching within documents. No two tools overlap in purpose, making selection unambiguous.
All tool names follow a consistent verb_noun pattern with snake_case, using list_, read_, and search_ prefixes. The slight singular/plural variation is natural and does not disrupt the pattern.
Three tools is appropriately scoped for a document access utility, covering the essential read-side operations without redundancy. The server feels focused and not bloated.
For a context-bridge server that provides document access, the ability to list, read, and search covers the core use cases. There is no obvious missing operation within the server's implied read-only scope.