revloop
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_account_contextB | Current facts (stage, amount, pains, objections, competitors, ...) for one account, with sources. |
| search_factsA | Search current facts by text across all accounts. Optional kind filter, e.g. 'competitor'. |
| propose_actionB | Propose an action (e.g. kind 'email_draft', 'crm_note', 'task'). Nothing is sent; a human approves. |
| list_pending_actionsB | Actions waiting for human approval. |
| outcome_reportC | Per playbook: share of accounts that advanced stage with an approved action vs a holdout. |
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 5 tools
list_pending_actions, propose_action, and outcome_report are clearly separated by purpose. get_account_context and search_facts both retrieve facts, but one is account-scoped and the other is cross-account text search, so the overlap is minor and descriptions help.
All names use snake_case and most follow a verb_noun pattern (list_pending_actions, get_account_context, search_facts, propose_action). outcome_report breaks the pattern as a noun phrase, but the overall convention is still readable and mostly consistent.
Five tools is well-scoped for a focused approval-loop server. Each tool covers a distinct part of the workflow: context lookup, fact search, action proposal, pending-action listing, and outcome reporting.
The set covers context retrieval, fact search, proposal, pending listing, and outcome reporting, but lacks approve/reject or action-detail operations. This leaves a notable gap in the approval lifecycle, even if human approval happens outside the MCP surface.