Loading ToolBench
Sinout MCP Server — Claude integration for workspace management, memory, budget, calendar, and custom tools
Server has 10 tools with basic naming and descriptions, but significant gaps in schema completeness and parameter documentation. Tool names follow verb_noun convention (sinout_setup_memory, sinout_list_budget_entries), which is good. However, most parameter descriptions are minimal (1-3 words), and several tools lack critical schema details. Output schemas are not documented. Error handling guidance is absent. The server appears to be a wrapper around a SinoutX workspace system, but the abstraction leaks implementation details (workspaceId, projectId) that should be resolved internally.
Add an income/expense entry to the legacy project budget. Pass projectId OR workspaceId (a project is resolved from it). NOTE: if you use the Finance MODULE, prefer sinout_create_record into its transactions/budget collection (sinout_list_collections) — that is the module data store.
Delegate a question or task to the built-in SinoutX assistant. It knows the workspace deeply and has 60+ tools (pages, tasks, search, modules/records, export to PDF/DOCX, Telegram, deep research). Use it for things it does better than you, or to act inside a workspace you share.
Create a new calendar event
Get budget summary (income, expenses, balance) for a project
Get upcoming calendar events for a workspace
Output schemas not documented. Tools return data but LLMs cannot predict field names, types, or structure. This forces agents to guess and wastes tokens on trial-and-error parsing.
Parameter descriptions are minimal (1-3 words). 'Project ID', 'Workspace ID', 'Filter by type' lack context on format, constraints, or when to use. LLMs cannot infer whether to pass UUIDs, names, or numeric IDs.
No error handling guidance. Tools do not document what errors can occur, whether they are retryable, or what the LLM should do next. A failed lookup returns nothing; no suggestion of alternatives.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 49 | 2026-07-28+ | v2 |
START HERE. Bootstrap EVERYTHING in one call: ensures you have a memory workspace (creates one + installs the Memory module if you have none — works from scratch), then returns your workspace, all module projects with their collections (by NAME + field schema, so no hardcoded IDs), your memory Core (soul rules), recent facts, and whether semantic recall is active. Idempotent — safe to call at the start of every session instead of setup_memory + reading resources + recall separately.
List budget entries (transactions) for a project
List calendar events for a project or workspace
Ensure this agent has its own memory workspace with the Memory («Память») module installed. Creates a workspace if none exists and installs the module (idempotent). Call once at the start of a session. Returns workspaceId and the memory collections (core/facts/entities/episodes) with their field schema.
Update a calendar event
Mutually exclusive parameters not documented. sinout_get_budget_summary accepts both projectId and workspaceId; unclear which takes precedence or if both are required. sinout_add_budget_entry has the same ambiguity.
No pagination support documented. sinout_list_budget_entries and sinout_list_events may return large result sets, but no limit, offset, or cursor parameters are visible. Risk of context window exhaustion.