MCP Blog API
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 |
|---|---|
| get_blogsB | Fetch all blogs from the mock API. |
| search_blogsC | Search for blogs by title using the mock API. |
| add_blogC | Add a new blog to the mock 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 3 tools
Each tool has a clearly distinct purpose: add_blog creates new blogs, get_blogs retrieves all blogs, and search_blogs finds blogs by title. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with snake_case: add_blog, get_blogs, and search_blogs. This predictability enhances readability and usability across the tool set.
With only 3 tools, the set feels thin for a blog API that typically requires CRUD operations. While the tools cover creation and retrieval, the absence of update and delete tools limits the server's scope, making it borderline appropriate.
The tool set is significantly incomplete for a blog API domain. It lacks update_blog and delete_blog tools, preventing full lifecycle management. This gap will likely cause agent failures when attempting to modify or remove blogs.