Skip to main content
Glama

AceRound AI Interview Copilot

suggest_hot_word_libraries

Read-only

Have AI pick the 2–4 official hotword libraries that best match a role name and description; returns library IDs and names. Nothing is saved; bind them with update_goal_hot_words. (Requires the user's sign-in with scope interviews:write.)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "jobName": "<jobName>"
    },
    "name": "suggest_hot_word_libraries"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobNameYesRole name
jobDescriptionNoRole description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Nothing is saved,' adding the important fact that selection is ephemeral. It also discloses a prerequisite that annotations cannot express: the user must be signed in with scope interviews:write — a non-obvious requirement for a read-only operation.

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?

A single dense sentence plus a parenthetical prerequisite — front-loaded with the action and payoff, with no filler. The parenthetical auth note is slightly grafted on but is short and load-bearing.

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 two-parameter tool with no output schema, the description covers what it returns (IDs and names), that no state is persisted, the follow-up tool needed to persist, and the auth prerequisite. An agent has everything needed to call it and act on the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters (jobName, jobDescription) are already documented in the schema. The description adds only the mapping of 'role name and description' to the inputs, plus the 2–4 result count, which is output behavior rather than parameter meaning.

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 names a specific verb and resource ('Have AI pick the 2–4 official hotword libraries that best match a role name and description') and states the return payload (library IDs and names). The matching/suggestion framing distinguishes it from a plain listing tool, though it never names a sibling to contrast with explicitly.

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?

It clearly routes the agent to the follow-up step: 'Nothing is saved; bind them with update_goal_hot_words,' which tells the caller what to do after receiving suggestions. It stops short of stating when not to use it (e.g., when the user already knows which library to bind).

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