Ventless Fireplace Review 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| site_overviewA | Return public metadata for Ventless Fireplace Review and explain the read-only scope of this server. |
| search_contentA | Search public published pages and posts on Ventless Fireplace Review by keyword. |
| list_contentA | List public published pages or posts with titles, URLs, dates, and excerpts. |
| get_contentA | Retrieve one public published page or post by its WordPress slug, converted to readable Markdown. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| homepage | Public Homepage content from Ventless Fireplace Review |
| mission | Public Our Mission content from Ventless Fireplace Review |
| about | Public About Ventless Fireplace content from Ventless Fireplace Review |
| editorial-policy | Public Editorial Policy content from Ventless Fireplace Review |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: overview for metadata, search for keyword lookup, list for enumeration, and get for retrieving a specific post. No functional overlap.
All tool names use snake_case and follow a verb-noun pattern (search_content, list_content, get_content), with site_overview being a minor exception but still clear and consistent in style.
The server is intentionally read-only for a single blog, and four tools cover the essential content retrieval operations without redundancy or excess.
The tool set fully covers the read-only domain: discovering metadata, searching, listing, and fetching individual content. No write operations are needed given the stated read-only scope.