moadim 1.7.4

Loop engine for AI agents — routines over REST, MCP, and a built-in web UI
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

//! MCP `get_lock_status` tool — mirrors `GET /routines/lock`, split into its own
//! `#[tool_router]` block so it can be combined with the rest of `mcp.rs`'s router.

use rmcp::{model::CallToolResult, tool, tool_router};

use super::{ok, MoadimMcp};
use crate::routes::get_lock_status::logic;

#[tool_router(router = get_lock_status_tool_router, vis = "pub(super)")]
impl MoadimMcp {
    /// Report whether the shared and/or local lock sentinels are present, mirroring
    /// `GET /api/v1/routines/lock`.
    #[tool(
        description = "Get the global routine lock status. Returns `shared` (committed .lock file), `local` (gitignored .local.lock), and `locked` (either is present)."
    )]
    #[allow(
        clippy::unused_self,
        reason = "tool_router dispatches every handler through self.method(...) uniformly"
    )]
    pub(super) fn get_lock_status(&self) -> Result<CallToolResult, rmcp::ErrorData> {
        Ok(ok(logic::build()))
    }
}

#[cfg(test)]
#[path = "mcp_tests.rs"]
mod mcp_tests;