Marginalia 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-marginaliaC | Search the web using Marginalia Search |
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-marginalia' has a clear and distinct purpose of searching the web using Marginalia Search, leaving no room for confusion or misselection.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'search-marginalia' follows a clear verb_noun pattern, and with no other tools to compare, there are no deviations or inconsistencies in naming conventions.
A single tool for a web search server is too few for the apparent scope, as it lacks basic functionality like filtering results, handling pagination, or accessing specific search features. This minimal toolset feels thin and limits the server's utility, making it borderline inadequate for typical search-related tasks.
The tool surface is severely incomplete for a web search domain. While 'search-marginalia' provides a core search function, there are significant gaps such as no ability to refine searches, view result details, or manage search history. This will likely cause agent failures when more complex search operations are needed.