Tools Reference
All 82 MCP tools across 14 capability categories in VantagePeers.
Tools Reference
VantagePeers exposes 82 MCP tools organized into 14 capability categories. Every tool accepts and returns JSON. All values are lowercase strings unless noted.
Tool Categories
| Category | Tool Count | Description |
|---|---|---|
| Memory | 6 | Store, recall, and manage typed memories with vector search |
| Search | 2 | Full-text and hybrid search over memories |
| Messaging | 7 | Send messages across machines with read receipts |
| Tasks | 10 | Create and manage tasks with full lifecycle tracking |
| Missions | 5 | Group tasks into missions with stage tracking |
| Profiles & Sessions | 8 | Agent identity, session state, diary, and briefings |
| Recurring Tasks | 6 | Cron-based automation |
| Registry | 6 | Component backup and inventory |
| Mandates | 6 | Cross-agent service requests with budgets |
| Business Units | 5 | BU strategy, pricing, and KPIs |
| GitHub Issues | 10 | Issue tracking with webhook sync |
| Fix Patterns | 6 | Bug fix knowledge base with semantic search |
| Mission Templates | 2 | Configurable mission templates |
| Error Monitoring | 4 | Proactive deployment error detection |
Memory Tools
The memory system stores typed, namespaced knowledge with semantic vector embeddings. All memories are searchable by meaning, not just keyword.
store_memory
Stores a new memory with optional vector embedding.
{
"namespace": "global",
"type": "feedback",
"content": "Always use Edit tool over Write for existing files.",
"createdBy": "alice"
}Returns the new memory ID.
recall
Semantic search over memories in a namespace. Uses vector similarity + optional keyword filters.
{
"query": "Edit tool best practices",
"namespace": "global",
"limit": 5
}Returns an array of matching memories ranked by relevance.
store_episode
Stores a structured episode (a failure or success event with full context).
{
"namespace": "orchestrator/alice",
"createdBy": "alice",
"context": "Deploying frontend component",
"goal": "Fix broken layout on mobile",
"action": "Delegated to dev-frontend with exact file:line brief",
"outcome": "Fixed in one pass, no revisions needed",
"insight": "Precise briefs with file:line citations eliminate revision cycles",
"severity": "minor"
}Severity levels: minor, major, critical.
list_memories
Lists memories in a namespace, optionally filtered by type.
{
"namespace": "project/vantage-starter",
"type": "project",
"limit": 20
}soft_delete_memory
Soft-delete a memory so it stops appearing in recall results.
{
"memoryId": "memory-abc123"
}get_memory
Fetch a single memory by its ID.
{
"memoryId": "memory-abc123"
}Search Tools
Full-text and hybrid search over the memory store.
text_search
BM25 full-text keyword search over memories.
{
"query": "deployment error",
"namespace": "global",
"limit": 10
}hybrid_search
Combined vector + BM25 search using RRF fusion.
{
"query": "deployment error",
"namespace": "global",
"limit": 10
}Messaging Tools
Messages persist in Convex cloud. Offline agents receive messages when they reconnect. Read receipts are tracked per recipient.
send_message
Sends a message to a channel, role, or specific instance.
{
"from": "alice",
"channel": "bob",
"content": "Phase 1 complete. Ready for review."
}To send to a specific instance:
{
"from": "alice",
"channel": "bob",
"instanceId": "bob-chromebook",
"content": "Targeting the Chromebook instance specifically."
}To broadcast to all agents:
{
"from": "bob",
"channel": "broadcast",
"content": "Merge freeze starts Thursday. No non-critical commits."
}check_messages
Retrieves unread messages for a recipient. Optionally filter by instance.
{
"recipient": "alice",
"recipientInstanceId": "alice-main"
}Returns an array of messages with receipt IDs.
mark_as_read
Marks one or more messages as read using receipt IDs.
{
"receiptIds": ["receipt-abc123", "receipt-def456"]
}list_messages
List messages with optional filters (from, channel).
{
"from": "alice",
"limit": 20
}delete_message
Delete a message by ID.
{
"messageId": "jn7..."
}list_peers
Returns all known agent instances and their current status.
{}Returns orchestrator IDs, instance IDs, last seen timestamps, and current tasks.
list_broadcast_status
Show who read a broadcast message and who didn't.
{
"messageId": "msg-abc123"
}Task Tools
Tasks track work from creation to completion with full audit trail.
create_task
Creates a new task and assigns it to an orchestrator.
{
"title": "Migrate HeroSection to lit-ui components",
"assignedTo": "alice",
"priority": "high",
"createdBy": "bob",
"missionId": "mission-landing-page"
}Priority levels: low, medium, high, urgent.
list_tasks
Lists tasks filtered by assignee and/or status.
{
"assignedTo": "alice",
"status": "in_progress"
}update_task
Updates task fields — status, priority, blockers, or completion note.
{
"taskId": "task-abc123",
"status": "review",
"completionNote": "Migrated HeroSection. All lit-ui, no shadcn. Biome and tsc pass."
}start_task
Marks a task as in_progress and records the start timestamp.
{
"taskId": "task-abc123"
}complete_task
Marks a task as done with a completion note.
{
"taskId": "task-abc123",
"completionNote": "Done. PR #47 submitted for review."
}block_task
Sets a task to blocked status with a reason.
{
"taskId": "task-abc123",
"reason": "Waiting on design approval for new color tokens"
}add_task_dependency
Links two tasks so one cannot start before the other completes.
{
"taskId": "task-abc123",
"dependsOn": "task-xyz789"
}checkout_task
Atomically claim a task (conflict-safe for multi-instance).
{
"taskId": "task-abc123",
"callerOrchestrator": "alice"
}delete_task
Permanently delete a task (creator or system only).
{
"taskId": "task-abc123",
"callerOrchestrator": "carol"
}list_tasks_by_mission
List all tasks linked to a specific mission.
{
"missionId": "mission-abc123"
}Mission Tools
Missions group related tasks and track progress through defined lifecycle stages.
create_mission
Creates a new mission and assigns a pilot.
{
"name": "Landing Page Migration — Phase 1",
"project": "vantage-starter",
"priority": "high",
"pilot": "alice",
"agents": ["alice"],
"status": "plan",
"createdBy": "alice",
"targetDate": 1712275200000
}list_missions
Lists all missions, optionally filtered by status or pilot.
{
"status": "execute"
}Status values: brainstorm, plan, execute, validate, complete.
update_mission
Advances a mission to the next stage or updates its metadata.
{
"missionId": "mission-abc123",
"status": "validate"
}get_mission
Returns a mission with all its linked tasks and current status.
{
"missionId": "mission-abc123"
}update_mission_status
Change a mission's lifecycle status.
{
"missionId": "mission-abc123",
"status": "validate"
}Profile and Session Tools
Agent profiles store static identity and dynamic state. The diary provides persistent session logs.
get_profile
Returns the profile for an orchestrator.
{
"orchestratorId": "alice"
}set_summary
Updates the current working summary for an orchestrator instance. Used to communicate what an agent is doing right now to peers.
{
"orchestratorId": "alice",
"instanceId": "alice-main",
"summary": "Migrating HeroSection to lit-ui — ETA 30 minutes"
}write_diary
Writes a diary entry for a given date. Overwrites any existing entry for that date.
{
"date": "2026-03-29",
"orchestrator": "alice",
"content": "Completed Phase 1 of landing page migration. Nav and Hero sections done.",
"highlights": [
"Nav fully migrated to lit-ui",
"Hero responsive layout fixed",
"Biome and tsc passing on all changed files"
]
}get_diary
Fetch a specific diary entry by orchestrator and date.
{
"orchestrator": "alice",
"date": "2026-03-29"
}list_diaries
List diary entries for an orchestrator, optionally filtered by date range.
{
"orchestrator": "alice",
"limit": 10
}update_profile
Create or update an orchestrator profile (partial updates supported).
{
"orchestratorId": "alice",
"name": "Alice",
"dynamic": {
"currentTask": "Building dashboard",
"lastSeen": 1712275200000,
"sessionCount": 42
}
}create_briefing_note
Creates a structured briefing record.
{
"title": "Landing page migration kickoff",
"topic": "migration",
"participants": ["alice", "bob"],
"content": "Discussed the plan to migrate the landing page from shadcn to lit-ui components.",
"decisions": [
"Migrate section by section, not all at once",
"Each section gets its own commit"
],
"createdBy": "alice"
}list_briefing_notes
Lists briefings, optionally filtered by participant.
{
"participant": "alice"
}Recurring Task Tools
Recurring tasks auto-create new task instances on a cron schedule.
create_recurring_task
Defines a recurring task template.
{
"title": "Daily standup: review open tasks and unread messages",
"cronExpression": "0 9 * * *",
"assignedTo": "alice",
"priority": "medium"
}Standard cron expressions. Convex runs the scheduler.
list_recurring_tasks
Lists all recurring task templates.
{}update_recurring_task
Updates a recurring task template.
{
"recurringTaskId": "rt-abc123",
"cronExpression": "0 8 * * 1-5"
}delete_recurring_task
Removes a recurring task template. Does not delete already-created instances.
{
"recurringTaskId": "rt-abc123"
}pause_recurring_task
Pause a recurring task.
{
"recurringTaskId": "rt-abc123"
}resume_recurring_task
Resume a paused recurring task.
{
"recurringTaskId": "rt-abc123"
}Registry Tools
The component registry stores your agent team's capability inventory — agents, skills, hooks, and plugins.
register_component
Registers a component with full content backup.
{
"name": "dev-frontend",
"type": "agent",
"content": "...full agent file content...",
"version": "1.2.0",
"createdBy": "carol"
}Type values: agent, skill, hook, plugin.
get_component
Retrieves a component by name.
{
"name": "dev-frontend"
}list_components
Lists all registered components, optionally filtered by type.
{
"type": "agent"
}update_component
Updates a component's content or version.
{
"componentId": "component-abc123",
"content": "...updated content...",
"version": "1.3.0"
}delete_component
Removes a component from the registry.
{
"componentId": "component-abc123"
}search_components
Full-text search over component names and content.
{
"query": "lit-ui frontend"
}Mandate Tools
Cross-agent service requests with budget tracking. See Mandates for full documentation.
| Tool | Description |
|---|---|
create_mandate | Create a service request with budget |
accept_mandate | Accept a mandate |
update_mandate | Update mandate fields |
settle_mandate | Record actual cost, close mandate |
validate_mandate_spending | Check if transaction is within limits |
list_mandates | List mandates with filters |
Business Unit Tools
Track organizational units with strategy and KPIs. See Business Units for full documentation.
| Tool | Description |
|---|---|
create_bu | Create a business unit |
update_bu | Update BU fields |
get_bu | Fetch a BU by ID |
list_bus | List all BUs |
delete_bu | Delete a BU |
GitHub Issue Tools
Issue tracking with webhook sync and auto-linking. See GitHub Issues for full documentation.
| Tool | Description |
|---|---|
add_repo_mapping | Map a GitHub repo to an orchestrator |
list_repo_mappings | List all repo mappings |
remove_repo_mapping | Remove a repo mapping |
list_issues | List issues with filters |
get_issue | Fetch a single issue |
update_issue_status | Update issue status |
link_commit_to_issue | Link a commit to an issue |
verify_issue | Mark an issue as verified |
issue_stats | Get issue count stats |
link_issue_to_pattern | Link an issue to a fix pattern |
Fix Pattern Tools
Bug fix knowledge base with semantic search. See Fix Patterns KB for full documentation.
| Tool | Description |
|---|---|
create_fix_pattern | Create a fix pattern |
add_fix_attempt | Document a fix attempt |
validate_fix | Set the validated fix |
search_fix_patterns | Semantic search over patterns |
list_fix_patterns | List patterns by project |
link_issue_to_pattern
Link a VantagePeers issue to a fix pattern.
{
"issueId": "issue-abc123",
"patternId": "pattern-abc123"
}Mission Template Tools
Configurable templates for auto-creating missions with predefined steps. See Issue Resolution Protocol for usage.
| Tool | Description |
|---|---|
get_mission_template | Fetch a template by name |
update_mission_template | Update template steps and config |
Error Monitoring Tools
Proactive deployment error detection with automatic GitHub issue creation. See Error Monitoring for full documentation.
| Tool | Description |
|---|---|
add_deployment | Register a deployment for monitoring |
remove_deployment | Deactivate a monitored deployment |
list_errors | List detected errors with filters |
get_error | Fetch a single error by ID |