Skip to main content
Glama
calebn

Podcast MCP

by calebn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_session_presence_tool

Retrieve who is in a Sharecut Studio session, including display names, cursors, selections, viewport, transport, 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.

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?

With no annotations, the description carries the full behavioral burden. It discloses the returned presence fields and adds genuine interpretive context for `viewport` (it is the window a follower should show, and it can begin at 0 and exceed the visible screen early in a phone's fixed-playhead timeline). It says nothing about read-only semantics, polling/cadence, permissions, or failure behavior, so the disclosure is partial rather than complete.

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?

Two front-loaded sentences: the field inventory first, then a targeted clarification of `viewport`. Tight and purposeful, though the viewport sentence is somewhat opaque without more context about the phone playhead case.

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?

The output schema exists, so the field enumeration is partly redundant, and the description omits the one thing the structured data cannot cover: the meaning of project_path and when to call this rather than get_session_state_tool. Adequate but with clear gaps for a presence/read tool.

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?

There is one parameter, project_path, with 0% schema description coverage, and the description never mentions it — not its meaning, nor what the null default implies (presumably the current session). With a single undocumented parameter, the description should have compensated and does not.

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 states a specific resource and enumerates exactly what presence data comes back: display names, cursor, selection, viewport, transport, and follow relationships. An agent can tell this is a read of live collaborative session state. However, it never distinguishes itself from the near-identical sibling get_session_state_tool, which is the main ambiguity.

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?

No when-to-use guidance, no prerequisites, and no mention of when to prefer this over get_session_state_tool or the many session_* mutation tools. The agent must infer usage entirely from the name.

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