lafe-blog 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 |
|---|---|
| create_noteB | Create a new note |
| write_noteC | Write a new note |
| post_blogC | Post a blog article to the CMS API using Zod validation |
| validate_blogB | Validate blog data using Zod schema without posting |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_notes | Summarize all notes |
| post_blog | use this prompt when publishing a cms blog |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| First Note | A text note: First Note |
| Second Note | A text note: Second Note |
TDQS
Scored across 4 tools
There is significant ambiguity between 'create_note' and 'write_note', which appear to serve the same purpose of creating/writing notes, making it unclear which tool to use for note creation. The blog-related tools ('post_blog' and 'validate_blog') are distinct from each other but overlap conceptually with the note tools in the broader content creation domain.
The tool names follow a consistent verb_noun pattern (e.g., create_note, post_blog, validate_blog, write_note), which is predictable and readable. The only minor deviation is that 'write_note' uses 'write' instead of 'create', but it still fits the overall naming convention.
With 4 tools, the count is borderline thin for a blog server, as it might lack operations like updating, deleting, or listing notes and blogs. However, it covers basic creation and validation, so it's not severely mismatched but feels slightly under-scoped.
There are significant gaps in the tool surface for a blog server: it includes creation and validation for blogs and notes but lacks update, delete, list, or get operations for either resource. This incomplete coverage will likely cause agent failures when trying to manage content beyond initial creation.