Skip to main content
Glama

AceRound AI Interview Copilot

list_my_hot_words

Read-only

List the user’s own hotword libraries with all their words. (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_my_hot_words"
  }
}

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 and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond that: an auth requirement with the specific scope (interviews:read) and the fact that the response is populated with the words inside each library, not just library metadata.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero padding; the resource and its scope come first, and the auth constraint is parked in a parenthetical so it does not obstruct the main statement. Every clause earns its place.

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 tool with full annotation coverage, the definition supplies the essentials: what is returned (libraries plus their words) and what credential is required. Minor gaps remain around whether results are paginated or ordered and how this differs from sibling listers, but nothing critical is missing.

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 description carries no parameter burden and the baseline applies. Nothing in the schema needs explanation that the description omits.

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 ("List the user's own hotword libraries") and adds a scope qualifier ("own") plus content detail ("with all their words"), which visibly separates it from the general sibling list_hot_word_libraries. It stops short of naming that sibling, so the differentiation is implied rather than explicit.

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 possessive "user's own" implies the use case is retrieving personal libraries rather than public ones, which is useful routing context. However, there is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer the boundary with list_hot_word_libraries and get_goal_hot_words.

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