Galdor is a Go framework/library for building agentic systems, not an MCP server. The single tool 'add' is defined in a test file (pkg/observability/tool_test.go), suggesting it is a test fixture rather than a production tool. The tool has a minimal description ('Add two integers') and a basic schema with two integer parameters. No evidence of MCP protocol implementation, transport layer, or server capability. The codebase appears to be an agent framework with OpenTelemetry integration, not an MCP-compliant tool server.

• Move tool definitions from test files to production code with explicit MCP tool registration.
• Expand tool description to 50-200 chars explaining: what it does, when to use it, what it returns, and any constraints (e.g., 'Adds two integers and returns their sum. Use for arithmetic operations. Returns an integer result or an error if overflow occurs.').
• Document the output schema explicitly: {"type": "object", "properties": {"result": {"type": "integer", "description": "The sum of a and b"}}}.
• Implement MCP protocol transport (HTTP or SSE) with proper tool registration, capabilities negotiation, and stateless request handling per spec 2026-07-28.
• Add error handling that returns actionable messages: 'Integer overflow: a + b exceeds max int64. Try smaller values.' instead of raw errors.