Skeleton MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging | false |
| API_KEY | Yes | Your API key for authentication | |
| API_TIMEOUT | No | Request timeout in seconds | 30 |
| API_BASE_URL | No | Base URL for the backend API | https://api.example.com/v1 |
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 |
|---|---|
| health_checkB | Check the health status of the MCP server. Returns: A dictionary with the server status and configuration info. |
| list_itemsA | List all items with optional filtering and pagination. Args: page: Page number (1-indexed) page_size: Number of items per page filter_name: Optional filter by name (case-insensitive contains) Returns: A dictionary containing: - items: List of item objects - total: Total number of items matching the filter - page: Current page number - page_size: Number of items per page |
| get_itemA | Get a specific item by ID. Args: item_id: The unique identifier of the item Returns: The item data if found Raises: ValueError: If the item is not found |
| create_itemB | Create a new item. Args: name: The name of the item (required) description: Optional description metadata: Optional key-value metadata Returns: The created item data including the generated ID |
| update_itemB | Update an existing item. Args: item_id: The unique identifier of the item to update name: New name (optional) description: New description (optional) metadata: New metadata (optional, replaces existing) Returns: The updated item data Raises: ValueError: If the item is not found |
| delete_itemC | Delete an item. Args: item_id: The unique identifier of the item to delete Returns: A confirmation message Raises: ValueError: If the item is not found |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| getting_started | A prompt to help users get started with this MCP server. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_status | Get the current server status. |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: create_item, delete_item, get_item, list_items, and update_item form a complete CRUD set for items, while health_check is a separate server management tool. The descriptions reinforce distinct actions on specific resources, eliminating any ambiguity.
All tools follow a consistent verb_noun pattern with snake_case throughout: create_item, delete_item, get_item, health_check, list_items, update_item. The naming is predictable and readable, with no deviations in style or convention.
With 6 tools, this server is well-scoped for managing items and checking server health. The count is appropriate, providing full CRUD operations plus a utility tool without being overly complex or insufficient for the domain.
The tool surface is complete for the item management domain, covering create, read (get and list), update, and delete operations with proper pagination and filtering. The health_check tool adds server monitoring, leaving no obvious gaps for core workflows.