Skip to main content
Glama

AceRound AI Interview Copilot

get_live_session_status

Read-only

Show the user's live interview, mock interview and assessment in progress: session ID, target, start time, expiry, whether the page is online, which client handles it (desktop app / web), and page state (started, AI answering, language, auto-answer, one card per question, etc.). (Requires the user's sign-in with scope interviews:read.)

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_live_session_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false with openWorldHint=false, so the safety profile is covered. The description adds real value by naming the required auth scope (interviews:read) and the breadth of returned state (client type, online flag, page state), but it does not say what happens when no session is active.

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?

The verb and scope are front-loaded and the trailing parenthetical efficiently lists the returned fields and the auth requirement, though the page-state enumeration is long enough to slightly dilute the single sentence.

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

Completeness4/5

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

With no output schema, the description correctly compensates by enumerating the returned fields and page states, and it discloses the required auth scope. The only gap is the no-active-session behavior for what is otherwise a well-covered zero-parameter read.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly avoids inventing any input semantics.

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 verb ('Show') and a precisely scoped resource (live interview, mock interview and assessment currently in progress), then enumerates the returned fields, so an agent can tell this apart from report/transcript tools like get_interview_report. It stops short of naming any sibling explicitly.

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

Usage Guidelines3/5

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

The 'in progress' framing implies the read context and the parenthetical gives a prerequisite (sign-in with scope interviews:read), but there is no explicit when-to-use/when-not guidance or pointer to the related control tools (answer_live_interview_now, end_live_interview, set_live_interview_options).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources