Skip to main content
Glama

workspace_sessions

Check active sessions and recent file writes in your workspace to detect concurrent edits before modifying files.

Instructions

Returns same-workspace session awareness: who else is actively connected to this project and what files they recently edited.

you — this session's name.

active_sessions — sessions on this workspace right now (name, client, how long since their last tool call). A single entry whose is_self field is true means you are the only active session — your view of the workspace is authoritative. Multiple entries mean concurrent agents are working here; treat any file a peer recently touched as potentially changed.

recent_writes — the last N mutating operations (write_file, edit_file, rename_file, git commit, …) by all sessions on this workspace. The file path (when available), session name, operation, and age are shown. A successful git commit is attributed in full: its line carries the session name, the commit's short SHA and subject, and the repository, so a peer's commit is traceable to the session that authored it. When [collab] peer_awareness is on and the topology index has the file, each entry is annotated with its enclosing package/symbol (best-effort, source=topology).

Use this before editing a file that another session may have recently modified: if it appears in recent_writes, re-read it first.

Parameters: recent_limit — max recent-write entries to return (default 10, max 50).

Workspace boundary: workspace_sessions is scoped to the caller's pinned workspace; it never reveals sessions from a different project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recent_limitNoMaximum recent-write entries to return (1–50; default 10).
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses workspace scoping, best-effort topology annotations, and the meaning of a single active session. However, it never explicitly states that the tool is read-only or has no side effects, which would make it fully transparent.

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 front-loaded with a summary, then organized with bolded field names and clear explanations. Every sentence adds value, including edge cases like git commit attribution and topology annotation, without being bloated.

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?

There is no output schema, so the description fully explains the return structure: 'you', 'active_sessions', and 'recent_writes' with each field's meaning. It also covers workspace boundary and practical usage, making it complete for this tool.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds no new parameter meaning; it repeats 'max recent-write entries to return (default 10, max 50)', which is already in the schema.

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 opens with 'Returns same-workspace session awareness: who else is actively connected to this project and what files they recently edited.' This uses a specific verb and resource, clearly distinguishing it from sibling tools like workspace_symbols or file_outline. The overall purpose is unmistakable.

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

Usage Guidelines4/5

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

It gives explicit usage guidance: 'Use this before editing a file that another session may have recently modified: if it appears in recent_writes, re-read it first.' This describes when to use the tool, but it doesn't mention alternatives or when not to use it, which prevents a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/plumbkit/plumb'

If you have feedback or need assistance with the MCP directory API, please join our Discord server