Skip to main content
Glama
ArkaAiAdmin

Agentic Memory

by ArkaAiAdmin

memory_coordinate

Coordinate multi-agent tasks, file locks, and messages using project state and task status updates.

Instructions

Multi-agent coordination tool for task management, file locking, and messaging.

Actions: create_task: Create a new task claim_task: Reserve a task for this agent update_task_status: Update task status (the primary coordination primitive) release_task: Release a task back to the pool complete_task: Mark task done, share result list_tasks: List tasks for a project lock_file: Acquire exclusive lock on a file unlock_file: Release file lock check_lock: Check if a file is locked send_message: Send message to another agent read_messages: Read pending messages get_project_state: See what others are doing update_project_state: Share what you're doing

Coordination model: Messages are notifications. Task status transitions are the ack. When Agent B reads a message and calls update_task_status, that IS the acknowledgement. No separate ack channel needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNo
valueNo
actionNoget_project_state
statusNo
payloadNo
task_idNo
to_agentNo
file_pathNo
task_typeNo
project_idNodefault
assigned_toNo
descriptionNo
message_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description explains the coordination model and lists all actions with brief explanations. It discloses the relationship between messages and task status updates. However, it lacks details on error handling or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and well-structured with a bullet list and a concluding paragraph. It is somewhat verbose but organized, with each sentence adding value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 13 parameters, 0% schema coverage, and no annotations, the description should provide detailed parameter guidance. It only gives high-level action descriptions and lacks specifics on required fields, return values, or behavior per action.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%. The description lists actions but does not specify which parameters are required for each action or their formats. The agent must infer parameter usage from action names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool is for multi-agent coordination, including task management, file locking, and messaging. It distinguishes from sibling tools which are primarily memory operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for multi-agent coordination but does not explicitly state when to use this tool versus alternatives. No when-not or alternative tool references are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

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/ArkaAiAdmin/Agentic-Memory'

If you have feedback or need assistance with the MCP directory API, please join our Discord server