Violett 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 |
|---|---|
| fetch_urlB | Fetch content from a URL via HTTP GET request |
| post_dataC | Send data via HTTP POST request |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_url | Summarize content from a URL |
| analyze_api | Analyze API response structure |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Violett Stream | A streaming resource for Violett server |
| Violett API Data | Data from Violett API |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: fetch_url performs HTTP GET requests to retrieve content, while post_data performs HTTP POST requests to send data. There is no overlap or ambiguity between them, as they target different HTTP methods and actions.
Both tools follow a consistent verb_noun pattern: fetch_url and post_data. The naming is predictable and readable, with no deviations in style or convention, making it easy for agents to understand their functions.
With only 2 tools, the server feels thin for a general-purpose HTTP client. While it covers basic GET and POST operations, it lacks other common HTTP methods (e.g., PUT, DELETE, PATCH) and related utilities (e.g., headers, authentication), making it under-scoped for typical HTTP tasks.
The tool surface is severely incomplete for an HTTP server. It only supports GET and POST, missing essential operations like PUT, DELETE, PATCH, and configuration tools for headers or authentication. This will cause agent failures when more complex HTTP interactions are needed.