Skip to main content
Glama
philipithomas

Contraption Company MCP

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

NameDescription
fetchB

Fetch a blog post using the MCP HTTP-style contract.

Accepts an id that can be a slug, canonical URL, or a post:// style identifier.

list_postsA

List blog posts with pagination.

Args: sort_by: Sort order - 'newest' or 'oldest' (default: 'newest') page: Page number (default: 1) limit: Number of posts per page, max 10 (default: 10)

Returns: List of post summaries with metadata

searchB

Search blog posts using semantic search.

Args: query: Search query text limit: Maximum number of results to return (default: 10)

Returns: List of search results with relevance scores

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: fetch retrieves a specific post by identifier, list_posts provides paginated listings with sorting, and search performs semantic queries. There is no overlap in functionality, and an agent can easily differentiate between them based on their descriptions.

Naming Consistency4/5

The naming is mostly consistent with a verb-based pattern (fetch, list_posts, search), but list_posts uses snake_case while the others are single words, creating a minor deviation. However, all names are clear and readable, with no chaotic mixing of conventions.

Tool Count5/5

With 3 tools, this server is well-scoped for a blog-focused domain. Each tool serves a distinct and essential function (retrieval, listing, and searching), making the count appropriate and efficient for the intended purpose without being overly sparse or bloated.

Completeness3/5

The tools cover read operations (fetch, list, search) effectively, but there are notable gaps for a full blog management system, such as create, update, or delete operations. While the read surface is complete, the lack of write capabilities limits the server's coverage for broader agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues