Skip to main content
Glama
Livus-AI
by Livus-AI

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WORKFLOWS_DIRNoThe directory where workflows are stored. By default, workflows are stored in the workflows/ directory.
SLACK_WEBHOOK_URLNoThe Slack webhook URL for the example_slack_message workflow

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
create_workflowA
Create a new Python workflow script.

Args:
    name: The name of the workflow (will be used as filename, e.g., "meeting_review_to_slack")
    description: A description of what the workflow does
    code: The Python code for the workflow. Must include a `run(params: dict = None) -> dict` function.

Returns:
    dict: Status of the operation with the file path

Example code structure:
    def run(params: dict = None) -> dict:
        params = params or {}
        # Your workflow logic here
        return {"status": "success", "result": "..."}
execute_workflowB
Execute a workflow script by name.

Args:
    name: The name of the workflow to execute
    params: Optional dictionary of parameters to pass to the workflow's run() function

Returns:
    dict: The result of the workflow execution
list_workflowsB
List all available workflow scripts.

Returns:
    dict: List of workflows with their metadata
read_workflowC
Read the source code of a workflow script.

Args:
    name: The name of the workflow to read

Returns:
    dict: The workflow source code and metadata
update_workflowB
Update an existing workflow script.

Args:
    name: The name of the workflow to update
    description: New description (optional, keeps existing if not provided)
    code: New Python code (optional, keeps existing if not provided)

Returns:
    dict: Status of the operation
delete_workflowC
Delete a workflow script.

Args:
    name: The name of the workflow to delete

Returns:
    dict: Status of the operation

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: create, delete, execute, list, read, and update workflows. The actions are mutually exclusive and target the same resource (workflows) with specific operations, making misselection unlikely.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with 'workflow' as the noun (e.g., create_workflow, delete_workflow). The naming is uniform and predictable, using snake_case throughout without any deviations.

Tool Count5/5

With 6 tools, the server is well-scoped for managing workflows, covering essential CRUD operations (create, read, update, delete) plus listing and execution. Each tool earns its place without being excessive or insufficient for the domain.

Completeness5/5

The tool set provides complete lifecycle coverage for workflows: creation, reading, updating, deletion, listing, and execution. There are no obvious gaps, and agents can perform all expected operations without dead ends in this domain.

Maintenance

ActivityInactive
ResponsivenessNo issues