Ressl AI 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_in_fileA | Search for a keyword within a specified file. Finds all occurrences including partial matches. |
| exact_word_searchA | Search for an exact word match within a specified file. Only matches complete words, not partial matches. |
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 overlapping purposes, both searching within files, with only subtle differences in matching behavior (exact word vs. keyword with partial matches). This creates ambiguity, as an agent might struggle to choose between them without understanding the nuanced distinction, and they could easily be confused for similar tasks.
The tool names follow a consistent snake_case pattern (exact_word_search, search_in_file) and use clear verbs ('search'), which aids readability. However, the naming is not perfectly consistent, as one specifies 'exact_word' while the other uses 'in_file', but overall, the pattern is predictable and coherent.
With only 2 tools, the server feels thin and under-scoped for a general-purpose AI MCP server, suggesting limited functionality. This low count may not adequately cover the domain implied by the server name, potentially leaving gaps in capabilities and making it less useful for agents.
Inferred as a file search domain, the tool set is severely incomplete, lacking basic operations like listing files, reading file contents, or handling multiple files. The two tools only cover specific search variations, leaving significant gaps that will likely cause agent failures in broader tasks.