Skip to main content
Glama

AceRound AI Interview Copilot

list_hot_word_libraries

Read-only

List the hotword libraries that can be bound to a target role: official libraries and the user’s own (isOwn=true), with IDs and names. Hotwords help speech recognition get proper nouns right. (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": "list_hot_word_libraries"
  }
}

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 safety is covered. The description adds value beyond them by disclosing the required auth scope ("interviews:read") and by describing the shape of the returned items (IDs and names).

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?

Three short sentences, front-loaded with the core scope before the supporting explanation and the auth requirement. The definitional aside ("Hotwords help speech recognition get proper nouns right") earns its place only marginally.

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 input parameters and no output schema, the description carries the burden of describing return contents, which it does (official vs. own libraries, IDs and names), and it flags the auth prerequisite. Only minor details such as ordering or result size are unaddressed.

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; there is nothing for the description to disambiguate. The mention of "isOwn=true" refers to a field in the returned data rather than an input, so it does not confuse parameter 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?

States a specific verb and resource ("List the hotword libraries") plus a scope qualifier ("that can be bound to a target role") and the composition of the result (official libraries and the user's own). An agent knows exactly what it gets back, though no sibling tool is named for contrast.

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 phrase "that can be bound to a target role" implies the usage context — enumerating candidates before binding one — but there is no explicit when-to-use statement, no when-not condition, and no named alternative (e.g., suggest_hot_word_libraries) to route between.

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