Skip to main content
Glama

面灵AI 面试助手

get_live_session_status

Read-only

查看用户当前进行中的实时面试、模拟面试与笔试:会话 ID、岗位、开始时间、到期时间,以及面试页是否在线、由哪一端执行(桌面客户端 / 网页)和页面状态(是否已点开始、AI 是否在作答、语言、自动回答、一题一卡等)。(需要用户授权,范围 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.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds genuinely new context by stating the authorization requirement and the required scope interviews:read, which an agent must know before calling. It does not discuss rate limits or behavior when no session exists, but the authorization disclosure is meaningful value beyond the annotations.

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?

Single sentence, front-loaded with the verb and scope, then the returned fields, then the auth note in parentheses. The long enumerated field list is verbose but earns its place because no output schema exists; minor cost is the trailing '等' (etc.) which slightly dilutes precision.

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?

For a no-parameter read tool with no output schema, the description covers everything an agent needs: what sessions are in scope, what fields come back, and the required authorization scope. Nothing material is missing for correct invocation.

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 does not invent parameter details and instead spends its words on what the response contains, which is the only semantics that matter for a no-arg call.

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 opens with a specific verb (查看) and a precisely scoped resource: the user's currently ongoing live interviews, mock interviews, and written exams, followed by the concrete fields returned (session ID, position, start/expiry time, online status, client type, page state). This clearly separates it from sibling mutation tools like end_live_interview or answer_live_interview_now, though it never names an alternative 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?

Usage is only implied by the scope phrase '当前进行中的' (currently ongoing), which tells the agent this is a status-polling tool for active sessions, but there is no explicit when-to-use/when-not-to-use guidance and no routing to a sibling for historical or report data (e.g. get_interview_report).

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