Synthetic Web Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SYNTHETIC_API_KEY | Yes | Your actual Synthetic API key from https://api.synthetic.new/ |
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_webC | Search the web using Synthetic API |
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 tool 'search_web' has a clear, distinct purpose that cannot be confused with any other tool in this set.
The single tool name follows a consistent verb_noun pattern ('search_web'), and with only one tool, there is no inconsistency to evaluate. The naming is straightforward and predictable.
A single tool for a web search server feels thin and limited in scope. While it covers the core search functionality, it lacks additional operations like filtering results, getting details, or handling multiple queries, making the server appear underdeveloped for its purpose.
The tool surface is severely incomplete for a web search domain. It only provides a basic search operation, missing essential features such as pagination, result refinement, or accessing specific search result details, which will likely cause agent failures in complex tasks.