Barnsworthburning MCP
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 |
|---|---|
| searchC | Search barnsworthburning.net for the given query |
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, as there are no other tools to confuse it with. The tool's purpose is clearly defined and distinct by default.
The single tool name 'search' follows a simple verb pattern, and with only one tool, there is no inconsistency to evaluate. The naming is inherently consistent within this minimal set.
A single tool is too few for most server purposes, as it severely limits functionality and scope, making the server feel thin and incomplete. This is a borderline case leaning toward inadequacy for typical MCP server expectations.
The server has a significant gap in coverage, as it only provides a search function without any complementary tools for creation, retrieval, update, or deletion of resources. This makes the surface severely incomplete for any meaningful domain beyond basic querying.