Skip to main content
Glama

面灵AI 面试助手

get_voiceprint_status

Read-only

查看用户是否已登记声纹(电话面试模式用它区分用户与面试官的声音)以及登记时间、声纹服务当前是否可用。声纹在发起面试的音频设置中录音登记。(需要用户授权,范围 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_voiceprint_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 the safety profile is covered. The description adds meaningful context beyond that: it discloses the required user authorization and the interviews:read scope, and it enumerates what the response conveys (registration status, registration time, service availability). This is solid added value, though it does not discuss failure modes or what happens when authorization is missing.

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 description is compact and front-loads the core purpose (checking voiceprint registration status) before adding the interview-mode rationale, the recording location, and the authorization scope. Every sentence contributes, with only minor redundancy in restating the interview-mode use case.

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?

For a zero-parameter read-only status tool with no output schema, the description is nearly complete: it explains what is checked, why it matters, where registration happens, and the authorization requirement. The only gap is that it does not describe the shape of the returned status values, which is a minor omission given the tool's simplicity.

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 there is no parameter semantics to explain. The baseline for a parameterless tool is 4, and nothing in the description detracts from that.

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 and resource: it checks whether the user has registered a voiceprint, the registration time, and whether the voiceprint service is available. It also explains the domain purpose (distinguishing the user's voice from the interviewer's in phone interview mode). It does not explicitly differentiate itself from the many sibling get_*_status tools, so it falls short of a 5.

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 implied through context: the voiceprint is used in phone interview mode and is recorded in the audio settings when initiating an interview. However, there is no explicit statement of when to call this tool versus alternatives, nor any exclusions or prerequisites beyond the authorization note.

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