fix(agent): improve ReAct parser and tool schemas for better LLM compatibility

- Fix ACTION_INPUT regex to properly capture multiline JSON responses
  - Changed from stopping at first newline to capturing all remaining text
  - Resolves parsing errors when LLM generates formatted JSON with line breaks

- Enhance tool schemas with detailed descriptions and parameter specifications
  - Add comprehensive Message schema for generate_text tool
  - Clarify distinction between resources/get (file read) and resources/list (directory listing)
  - Include clear usage guidance in tool descriptions

- Set default model to llama3.2:latest instead of invalid "ollama"

- Add parse error debugging to help troubleshoot LLM response issues

The agent infrastructure now correctly handles multiline tool arguments and
provides better guidance to LLMs through improved tool schemas. Remaining
errors are due to LLM quality (model making poor tool choices or generating
malformed responses), not infrastructure bugs.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

crates/owlen-mcp-client/Cargo.toml

@@ -0,0 +1,12 @@
+[package]
+name = "owlen-mcp-client"
+version = "0.1.0"
+edition = "2021"
+description = "Dedicated MCP client library for Owlen, exposing remote MCP server communication"
+license = "AGPL-3.0"
+
+[dependencies]
+owlen-core = { path = "../owlen-core" }
+
+[features]
+default = []

crates/owlen-mcp-client/src/lib.rs

@@ -0,0 +1,19 @@
+//! Owlen MCP client library.
+//!
+//! This crate provides a thin façade over the remote MCP client implementation
+//! inside `owlen-core`. It re‑exports the most useful types so downstream
+//! crates can depend only on `owlen-mcp-client` without pulling in the entire
+//! core crate internals.
+
+pub use owlen_core::mcp::remote_client::RemoteMcpClient;
+pub use owlen_core::mcp::{McpClient, McpToolCall, McpToolDescriptor, McpToolResponse};
+
+// Re‑export the Provider implementation so the client can also be used as an
+// LLM provider when the remote MCP server hosts a language‑model tool (e.g.
+// `generate_text`).
+// Re‑export the core Provider trait so that the MCP client can also be used as an LLM provider.
+pub use owlen_core::provider::Provider as McpProvider;
+
+// Note: The `RemoteMcpClient` type provides its own `new` constructor in the core
+// crate. Users can call `RemoteMcpClient::new()` directly. No additional wrapper
+// is needed here.