Skip to main content
Glama
Podcast MCP
by calebn

get_session_presence_tool

Retrieves who is present in a ShareCut Studio session plus each participant's cursor, selection, viewport, transport state, and follow relationships.

Instructions

Who is in the ShareCut Studio session: display names, cursor, selection, viewport, transport, follow relationships.

viewport is the time window a follower should show. Near the start of a phone's fixed-playhead timeline it begins at 0 and can be wider than what is on that screen.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_session_presence_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / project_path / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / project_path / default
      Added value: +null
    • removedInput schema / properties / project_path / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
      -  "project_path"
      -]
  2. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the shape of the returned presence data and explains the non-obvious `viewport` semantics (a follower's time window, starting at 0 near the start of a fixed-playhead phone timeline and potentially wider than the visible screen), which is genuine value. It never states that this is a read-only, side-effect-free snapshot, nor whether presence is live or cached, nor anything about cost or polling frequency — gaps that matter for a presence feed with zero annotation coverage.

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

Conciseness4/5

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

Front-loaded with the payload list in one line, then a focused second paragraph that exists solely to disambiguate `viewport`, which is the one term an agent would otherwise misread. No filler, though the second paragraph is somewhat niche relative to the whole tool.

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

Completeness3/5

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

An output schema exists, so the description does not need to enumerate return fields — yet it spends most of its length doing so, while leaving the only input parameter, the read-only nature of the call, and the boundary with get_session_state_tool unexplained. Adequate for a simple one-parameter read, but the effort is allocated to the least necessary part.

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

Parameters2/5

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

The single parameter `project_path` has 0% schema description coverage and is never mentioned in the description. Since coverage is far below 50%, the description was expected to compensate by explaining what the path identifies and what the default (null) means — it does neither.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource concretely — session presence — and enumerates the information it returns (display names, cursor, selection, viewport, transport, follow relationships), so an agent knows exactly what data it gets. It stops short of distinguishing itself from the obvious sibling get_session_state_tool, which is a meaningful gap in a catalog containing both.

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

Usage Guidelines2/5

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

There is no explicit when-to-use statement, no exclusions, and no reference to an alternative. The agent must infer from the field list alone that this is the 'who else is here and what are they doing' query, and must guess how it differs from get_session_state_tool.

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

Deploy Server

Other Tools