waiting-on
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| waiting_on_refreshB | Refresh waiting-on from Gmail_multi or a fixture. |
| waiting_on_refresh_agentsB | Refresh agent-thread open loops (Claude Code + Codex sessions). |
| waiting_on_refresh_voiceA | Refresh voice-queue open loops (JSONL event log; observe-only). |
| waiting_on_loopsC | Open loops across all allowed domains and channels. |
| waiting_on_listB | List tracked threads by ball or state (alias of loops). |
| waiting_on_showC | Show one thread with evidence snippets. |
| waiting_on_draft_replyC | Preview or create a Gmail draft. Never sends. |
| waiting_on_healthC | Show waiting-on health. |
| waiting_on_exportD | Export waiting-on data. |
| waiting_on_lead_listC | List manual leads (our ball first). Filters: status/ball/org/match/domain. |
| waiting_on_lead_addC | Add one manual lead. Requires name, channel, and ball. |
| waiting_on_lead_bumpC | Set who has the ball and record a note. Transactional; returns a structured conflict on a lost race. |
| waiting_on_lead_done | Mark a lead done. Transactional; returns a structured conflict on a lost race. |
| waiting_on_lead_edit | Edit a lead's due/org/contact/notes in place. Transactional; returns a structured conflict on a lost race. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/arkaigrowth/waiting-on'
If you have feedback or need assistance with the MCP directory API, please join our Discord server