XMemo

Open Project Workspace

open_project_workspace

Read-onlyIdempotent

Open the Project Workspace. With no project reference it always opens Project Workspaces Home — the caller's authorized project list — even when exactly one project is accessible. An exact project_id, or a project name/alias matching exactly one authorized project, opens that project's eight tabs (overview, memory, todo, decisions, documents, conversations, timeline, settings); multiple or no matches return Home with candidates or an honest no-match state. For a quick text-only status, blockers, or next-actions answer use get_project_summary. Explicit standalone TODO or Ledger intent keeps using open_todo_board or open_ledger.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`project`	No	Natural-language project name or alias; resolved only within your authorized projects, never a global search.
`project_id`	No	Optional project identifier to filter the Ledger or TODO workspace.
`initial_tab`	No	Project Workspace tab to open first: overview, memory, todo, decisions, documents, conversations, timeline, or settings. Legacy ledger values open Overview; use open_ledger for the standalone Ledger.	overview
`source_mode`	No	Post-authorization presentation policy: focused on this project, or all_authorized sources.	focused

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed17 schema fields changedAug 7, 2026

addedOutput schema / $defs / ProjectTabPageOutput / properties / generatedAt / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / $defs / ProjectTabPageOutput / properties / generatedAt / type
```
Removed value: -"string"
```

addedOutput schema / $defs / ProjectTabPageOutput / properties / requestId / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / $defs / ProjectTabPageOutput / properties / requestId / type
```
Removed value: -"string"
```

changedOutput schema / $defs / ProjectTabPageOutput / required

Previous value: -[
-  "schemaVersion",
-  "requestId",
-  "generatedAt",
-  "tab",
-  "page",
-  "providers"
-]New value: +[
+  "schemaVersion",
+  "tab",
+  "page",
+  "providers"
+]

addedOutput schema / $defs / ProjectWorkspaceOutput / properties / generatedAt / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
removedOutput schema / $defs / ProjectWorkspaceOutput / properties / generatedAt / type
```
Removed value: -"string"
```

addedOutput schema / $defs / ProjectWorkspaceOutput / properties / requestId / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / $defs / ProjectWorkspaceOutput / properties / requestId / type
```
Removed value: -"string"
```
addedOutput schema / $defs / ProjectWorkspaceOutput / properties / snapshotId / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
removedOutput schema / $defs / ProjectWorkspaceOutput / properties / snapshotId / type
```
Removed value: -"string"
```

changedOutput schema / $defs / ProjectWorkspaceOutput / required

Previous value: -[
-  "schemaVersion",
-  "requestId",
-  "snapshotId",
-  "generatedAt",
-  "project",
-  "activeTab",
-  "tabManifest",
-  "overview",
-  "navigation",
-  "sourceSummary"
-]New value: +[
+  "schemaVersion",
+  "project",
+  "activeTab",
+  "tabManifest",
+  "overview",
+  "navigation",
+  "sourceSummary"
+]

addedOutput schema / $defs / ProjectWorkspacesHomeOutput / properties / generatedAt / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
removedOutput schema / $defs / ProjectWorkspacesHomeOutput / properties / generatedAt / type
```
Removed value: -"string"
```
addedOutput schema / $defs / ProjectWorkspacesHomeOutput / properties / requestId / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
removedOutput schema / $defs / ProjectWorkspacesHomeOutput / properties / requestId / type
```
Removed value: -"string"
```

changedOutput schema / $defs / ProjectWorkspacesHomeOutput / required

Previous value: -[
-  "schemaVersion",
-  "requestId",
-  "generatedAt",
-  "surface",
-  "counts",
-  "projects",
-  "filters",
-  "noMatch",
-  "messageKey",
-  "dataQuality",
-  "errors"
-]New value: +[
+  "schemaVersion",
+  "surface",
+  "counts",
+  "projects",
+  "filters",
+  "noMatch",
+  "messageKey",
+  "dataQuality",
+  "errors"
+]

AddedJul 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false), the description reveals resolution rules: no reference always opens Home even with one accessible project, exact matches open the eight tabs, multiple/no matches return Home with candidates or no-match state, and legacy ledger values open Overview. This is valuable behavioral context not available in annotations.

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

Conciseness5/5

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

The description is dense yet well-structured: it opens with the core action, then sequentially covers parameter resolution, tab enumeration, edge cases, and sibling differentiation. Every sentence contributes meaningful information, with no filler or redundancy.

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

Completeness5/5

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

Given the tool's complexity (4 parameters, 8 tabs, multiple edge cases), the description is fully complete: it covers no-reference behavior, match resolution outcomes, tab list, legacy handling, and alternative tools. The presence of an output schema reduces the need to describe return values, and annotations cover safety, so the description fills all remaining gaps.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds important meaning: it explains project resolution logic (exact project_id vs. unique name/alias), outcome on multiple/no matches, and the initial_tab legacy behavior. This enriches the schema parameter descriptions with practical consequences.

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 uses the specific verb 'Open' with the resource 'Project Workspace' and lists the eight tabs, clearly distinguishing it from siblings like get_project_summary, open_todo_board, and open_ledger. It states exactly what the tool does: opens Home or a specific project's workspace.

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

Usage Guidelines5/5

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

Explicit guidance is given for when to use alternatives: 'For a quick text-only status, blockers, or next-actions answer use get_project_summary. Explicit standalone TODO or Ledger intent keeps using open_todo_board or open_ledger.' The description also clarifies behavior with no project reference, making the usage context unambiguous.

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

All XMemo tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation3/5

Multiple memory-retrieval tools (recall, search_memory, recall_context, read_memory, memory_overview) have overlapping purposes; detailed descriptions help but an agent could easily pick the wrong one. Similarly, ledger/open_ledger and todo/open_todo_board split text vs UI interaction, and forget overlaps with todo delete_all and ledger deletion.

Naming Consistency3/5

Most tools follow a verb_noun snake_case pattern (read_memory, update_memory, search_memory, open_ledger). However, several tools use bare nouns or verbs (forget, ledger, project, todo, recall, remember) and memory_overview is noun_noun, creating inconsistent conventions.

Tool Count3/5

19 tools is on the heavy side for the apparent scope, and the surface includes several pairs that duplicate the same domain in text vs UI form (ledger/open_ledger, todo/open_todo_board). Still, the count is defensible given the combined memory, project, TODO, and ledger coverage.

Completeness4/5

Memory has full lifecycle coverage (remember, read, search/recall, update, forget, restore), and TODO and Ledger workflows are largely complete. Minor gaps exist—no explicit project deletion and no pure text list-projects tool—but core workflows do not dead-end.

Open Project Workspace

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources