MCP-Bocha
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 |
|---|---|
| mcp-bocha_searchC | Search the web for information |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'mcp-bocha_search' has a clear and distinct purpose of searching the web for information, leaving no room for confusion or misselection.
The naming is perfectly consistent as there is only one tool. It follows a clear verb_noun pattern ('search' as the verb and implied 'web' as the noun), and with no other tools to compare against, there is no inconsistency in naming conventions.
A single tool is too few for most server purposes, as it typically feels thin and limits functionality. While a search tool can be useful, the server's scope appears narrow with only one operation, which may not cover the full domain of web search or related tasks adequately.
The tool surface is severely incomplete for a web search domain. It only provides a search function without any complementary tools for refining results, accessing cached pages, or handling different search types (e.g., images, news). This creates significant gaps that could lead to agent failures in more complex tasks.