Skip to main content
Glama
kerodkibatu
by kerodkibatu

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

NameDescription
imploreA

This tool launches a separate GUI process to show a quiz with one or more questions and waits for the user to respond. Multiple choice questions include an automatic "Other..." option with text input for additional flexibility. Perfect for clarifying requirements, getting decisions, or extracting implicit knowledge from users.

Args: questions: A list of question objects. Each question object should have: - text (str): The question text - type (str): Either "multiple_choice" or "free_form". For "multiple_choice", an automatic "Other..." radio button with text input is included after the options. - options (list, optional): List of options for multiple choice questions - id (str, optional): Unique identifier (auto-generated as "q1", "q2", etc. if not provided) title: The title of the dialog window (default: "Human Input Requested")

Returns: Dictionary with structured response: - On success: {"success": True, "answers": {question_id: answer, ...}} - On cancel: {"success": False, "cancelled": True} - On error: {"success": False, "error": "error message"}

Notes:

  • Unanswered multiple choice questions return null

  • Unanswered free-form questions return empty string ""

  • Prefer using comprehensive multiple choice options for most questions to provide structured choices, reserving free-form for simple copy-paste values or easily answered open questions. The automatic "Other..." option in multiple choice provides flexibility for cases not covered by the options.

Examples: Single question: implore(questions=[ { "id": "api_key", "text": "What is your API key?", "type": "free_form" } ])

Multiple questions:
implore(questions=[
    {
        "id": "framework",
        "text": "Which framework should we use?",
        "type": "multiple_choice",
        "options": ["React", "Vue", "Angular"]
    },
    {
        "id": "requirements",
        "text": "Any additional requirements?",
        "type": "free_form"
    }
])

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap with other tools. The tool 'implore' has a single, clearly defined purpose: launching a GUI quiz for user input.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'implore' is a clear verb that accurately describes its function of requesting human input.

Tool Count2/5

A single tool is too few for a server's purpose, as it limits functionality and forces all interactions through one interface. This makes the server feel thin and underdeveloped, lacking the depth needed for robust agent workflows.

Completeness3/5

The tool covers its specific domain of user input collection well, but the server's overall scope is unclear. As a standalone tool, it lacks related operations (e.g., managing saved responses or batch processing), leaving gaps in a broader human-in-the-loop workflow.

Maintenance

ActivityInactive
ResponsivenessNo issues