Skip to main content
Glama
MishaelOliva

proactive-agent-mcp

by MishaelOliva

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": false
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
poll_event_queueA

Claim unprocessed events from the proactive triage queue and take a time-boxed lease on each. Events whose lease lapses return to the queue automatically, so a crashed agent does not strand work.

complete_eventA

Settle a claimed event with an outcome and an optional note. Use this once triage of an event has finished.

release_eventA

Return a claimed event to the unprocessed pool without settling it, so another worker can pick it up immediately instead of waiting for the lease to lapse.

push_eventA

Record an observation the agent made onto the triage queue so it becomes visible to other workers. Rejected when the queue is full.

evaluate_document_complianceA

Check an extracted document against a declared schema. Reports missing required fields, pattern violations, a confidence score, and a triage verdict. This is deterministic field validation over regex rules, not document understanding.

query_rag_knowledgeA

Rank the built-in knowledge corpus against a query using sparse TF-IDF vectors and cosine similarity. Lexical rather than semantic: it matches vocabulary, so paraphrased queries retrieve poorly. Returns measured retrieval latency and an explicit grounding verdict.

request_human_approvalB

Park a sensitive action behind a human decision and return an authorization ticket. The confirmation code is never returned here: it must be supplied by an authorized human over an authenticated out-of-band channel, otherwise the gate proves nothing.

verify_approval_tokenA

Verify a supervisor's confirmation code against a ticket and consume the ticket on success. The code is bound to the action name, a digest of the action parameters, and the expiry, and each ticket is single-use.

track_cost_budgetA

Book token spend against a session budget. Once a session exceeds its budget the server refuses further tool calls for it until the budget is raised; enforcement is server-side, not advisory.

set_active_sessionA

Select which session the server's budget guard charges. The server refuses non-guardrail tool calls for any session that has exhausted its budget.

Prompts

Interactive templates invoked by user choice

NameDescription
autonomous_triage_loopRunbook for a proactive triage pass: claim queue events, validate documents, settle what was handled, and escalate what was not.
compliance_audit_briefGenerate an executive discrepancy brief for one evaluated document.

Resources

Contextual data attached and managed by the client

NameDescription
System Health & Runtime TelemetryUptime, process resource usage, negotiated protocol version, budget and approval-ticket counters, and triage queue depth.
Organizational Compliance PoliciesCompliance requirements for asset onboarding, agent governance, and data handling.

TDQS

A3.9/5.0

Scored across 10 tools

Disambiguation4/5

The tools cluster into four clear domains: event-queue lifecycle (poll/complete/release/push), approval (request/verify), budget (track/set_active_session), and two standalone capabilities (compliance, RAG). complete_event vs release_event could be momentarily confused, but the descriptions clearly distinguish settling from returning to the pool. set_active_session and track_cost_budget are related but have distinct roles.

Naming Consistency5/5

Every tool follows a consistent verb_noun snake_case pattern (poll_event_queue, complete_event, verify_approval_token, track_cost_budget, etc.). No mixed conventions or vague verbs anywhere in the set.

Tool Count5/5

Ten tools is well within the sweet spot for a triage/guardrail agent, and each tool earns its place by covering a distinct operation rather than duplicating another. No bloat or thin coverage.

Completeness4/5

The event queue has full lifecycle coverage (push/poll/complete/release), approval has request+verify, and budget has tracking plus session selection. Minor gaps like inspecting queue depth or listing pending events exist, but agents can work around them via polling.