Skip to main content
Glama

AceRound AI Interview Copilot

get_voiceprint_status

Read-only

Show whether the user has enrolled a voiceprint (used in phone-interview mode to tell the user's voice from the interviewer's), when, and whether the voiceprint service is available. Enrollment is done by recording in the audio settings when starting an interview. (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_voiceprint_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/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 behavior needs no restating. The description adds genuinely new context: the required sign-in scope (interviews:read) and the fact that it does not enroll but only reports. It does not describe response shape beyond the three facets, so the gain over annotations is moderate.

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 core question it answers, then the domain explanation, then the enrollment pointer and auth requirement. Every clause carries information, though the parenthetical definition plus the enrollment sentence make it slightly denser than needed for a zero-parameter read.

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 simple, zero-parameter read with no output schema, the description is complete: it names the three values returned, the prerequisite permission, and the out-of-band enrollment path. An agent has everything needed to call it correctly and interpret the result.

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 schema carries no semantics to supplement; the description correctly says nothing about inputs and instead frames the call as a whole-account status query.

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

Purpose5/5

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

States a specific query and enumerates exactly what it reports: enrollment existence, enrollment time, and service availability. It also defines the domain term ('used in phone-interview mode to tell the user's voice from the interviewer's'), so the agent can tell this apart from the general status siblings such as get_live_session_status or get_sms_relay_status.

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

Usage Guidelines4/5

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

The description gives clear context for when the tool is relevant (checking voiceprint enrollment/service availability for interview mode) and even explains that enrollment itself happens elsewhere, in the audio settings recording flow, which implicitly rules this tool out as an enrollment action. It stops short of explicit when-not guidance or naming an alternative diagnostic tool.

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