vremly
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VREMLY_API_KEY | Yes | Your organization API key. | |
| VREMLY_API_URL | No | API base URL. | https://api.vremly.com |
| VREMLY_OPENAPI_PATH | No | Point at a different OpenAPI document. | |
| VREMLY_MCP_READ_ONLY | No | Set to '1' to refuse anything but GET/HEAD/OPTIONS. | |
| VREMLY_MCP_TIMEOUT_MS | No | Per-request timeout. | 30000 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vremly_search_endpointsA | Search the Vremly API for endpoints by keyword. The API has 1037 operations covering projects (shoots), customers, media and delivery, invoicing, scheduling, the marketplace and webhooks. Start here when you do not already know the exact path. Returns method, path, summary and tags — pass a result to vremly_describe_endpoint for its full shape. |
| vremly_describe_endpointA | Describe one Vremly endpoint in full: path and query parameters, the request body schema with required fields, response schemas, and which credential it accepts. Call this before vremly_request so the body you send matches what the server validates — unknown fields are stripped silently rather than rejected, so a misspelled key fails invisibly. |
| vremly_requestA | Call a Vremly API endpoint and return its status and body. Authenticates with the configured organization API key; the organization is derived from that key, so it can only ever reach that organization's data, and the key's scopes decide what it may do (a READ key cannot write). Substitute real ids into the path — do not send {placeholders}. |
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 role: search finds endpoints, describe gives full schema details, and request executes the call. There is no overlap or ambiguity between them.
All tools share the vremly_ prefix and use snake_case, making the set predictable. The only minor inconsistency is that vremly_request omits the 'endpoint' object present in the other two names.
Three tools is an elegant fit for an API gateway covering 1,037 operations. Each tool earns its place in a clear discovery-to-execution pipeline without redundancy.
The workflow is complete: search to find endpoints, describe to understand the required shape, and request to execute. There are no obvious dead ends or missing operations for the stated purpose of interacting with the Vremly API.