Skip to main content
Glama

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
interactive_feedbackA

Ask the human user for interactive feedback through the Web UI.

Use this tool whenever you need a human decision, clarification, confirmation, plan approval, design review, or final sign-off before continuing — especially when the next step has multiple valid approaches, irreversible side effects, or significant trade-offs.

Behavior:

  • Renders the resolved message (Markdown) and an optional list of options in a Web UI; the user submits text + selected options + optional images.

  • The call blocks until the user submits, the auto-resubmit countdown expires, or the configured backend timeout is reached.

  • On success, returns a list of MCP content blocks (text + image) that include the user reply, selected options, and an optional prompt suffix.

  • On parameter validation failure, raises ToolError so the agent can retry with corrected arguments. On service / task failure, returns a configurable resubmit prompt instructing the agent to call this tool again, instead of silently dropping the request. After 3 failures in a row it returns the cause instead: stop calling and tell the user.

Cross-tool compatibility:

  • summary / prompt are accepted as aliases for message so the same mcp.json config can target other feedback MCP variants without retraining the agent.

  • options is an alias for predefined_options.

  • project_directory, submit_button_text, timeout, timeout_seconds, feedback_type, priority, language, tags, user_id, task_id are accepted but ignored. They prevent the first-call validation failures observed when an agent reuses arguments shaped for a different feedback MCP server.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Server InfoSelf-information for ai-intervention-agent MCP server. Returns version, transport, runtime details, middleware chain, accumulated error stats, Web UI runtime status, and task-queue snapshot as JSON.

TDQS

A4.6/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so no selection ambiguity is possible. Its purpose (soliciting human feedback via a Web UI) is stated explicitly and cannot be confused with anything else on the server.

Naming Consistency5/5

The lone tool uses a clear snake_case verb_noun name (`interactive_feedback`) consistent with common MCP conventions. With a single tool there is no opportunity for convention mixing.

Tool Count4/5

The server's scope is deliberately narrow — one blocking human-in-the-loop request — so a single tool is defensible rather than thin. A slightly richer surface (e.g. a non-blocking/poll variant) would justify a higher score, but nothing here is redundant.

Completeness4/5

The ask-feedback lifecycle (render message/options, block, return reply, retry on failure, then surface cause after 3 failures) is well covered, including tolerance for alias parameters from sibling servers. Minor gaps exist: no way to query pending/previous feedback or to check status without issuing a new request.

Maintenance

ActivityActive
ResponsivenessNo issues