SIMPA
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLM_MODEL | No | LLM model in LiteLLM format (e.g., 'ollama/llama3.2' or 'openai/gpt-4') | ollama/llama3.2 |
| DATABASE_URL | Yes | PostgreSQL connection URL (required) | |
| AZURE_API_KEY | No | Azure OpenAI API key (required if using Azure) | |
| GEMINI_API_KEY | No | Google Gemini API key (required if using Gemini models) | |
| OPENAI_API_KEY | No | OpenAI API key (required if using OpenAI models) | |
| EMBEDDING_MODEL | No | Embedding model name | nomic-embed-text |
| OLLAMA_BASE_URL | No | Ollama API base URL | http://localhost:11434 |
| ANTHROPIC_API_KEY | No | Anthropic API key (required if using Anthropic models) | |
| EMBEDDING_PROVIDER | No | Embedding provider: 'ollama' or 'openai' | ollama |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| refine_promptA | Refine a prompt before sending to an agent. Given an original prompt and context, either selects an existing refined prompt or creates a new one optimized for the agent type and language. Scoping Options (Optional but Recommended):
To improve focus and reduce context overload, include in the
Note: A project_id is required. If not provided, the response will include a list of existing projects or instructions to create one. The agent should:
|
| update_prompt_resultsA | Update prompt performance metrics after agent execution. Records the outcome of using a refined prompt and updates the prompt's statistics for future refinement decisions. Scoping Feedback:
Use |
| health_checkA | Health check endpoint. Returns the health status of the SIMPA MCP service. Examples:
Request (no parameters needed):
Returns: Service health status with version and timestamp |
| create_projectA | Create a new project for organizing prompts. Creates a project with language and dependency metadata to enable better prompt selection based on project context. Project Structure & Scoping:
Projects can define their default structure via
This helps downstream agents understand the project layout and scope their work appropriately without needing to explore the entire codebase. |
| get_projectA | Retrieve project information by ID or name. Look up a project by either its ID (UUID) or name. Project Scoping for Agents:
Returns
Use this structure when refining prompts to help agents understand the codebase layout and scope their work appropriately. |
| list_projectsA | List all projects with optional filtering. Retrieves a paginated list of projects, optionally filtered by programming language. Project Scoping:
Each project may include
Use |
| activate_promptA | Activate a previously deactivated prompt. Reactivates a prompt so it can be used in future refinement searches. |
| deactivate_promptA | Deactivate a prompt so it won't be used in searches. Soft-deletes a prompt by marking it as inactive. The prompt remains in the database but won't appear in search results or be used for finding similar prompts. |
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 8 tools
Each tool has a distinct purpose: refine_prompt handles prompt optimization, update_prompt_results tracks metrics, health_check monitors service status, create/get/list_projects manage project metadata, and activate/deactivate_prompt control prompt lifecycle. No two tools overlap in function.
Most tools follow a consistent verb_noun pattern (refine_prompt, create_project, list_projects, activate_prompt, etc.). The exception is health_check, which is a noun phrase rather than a verb_noun, making it slightly inconsistent but still readable.
With 8 tools, the server is well-scoped for a prompt management system. Each tool covers a necessary function—project management, prompt refinement, result tracking, and lifecycle control—without redundancy or bloat.
The core workflows are covered: project creation and lookup, prompt refinement and deactivation, result feedback, and health checks. Missing project update/delete operations and a dedicated get_prompt tool are minor gaps that agents can work around, but the surface is largely complete.