Skip to main content
Glama

AceRound AI Interview Copilot

generate_hot_words

Read-only

Have AI generate proper nouns that will come up in the interview and that speech recognition tends to get wrong, from a role name, description and optional resume. Nothing is saved; store them with create_hot_word_library / update_hot_word_library or update_goal_hot_words. Resume ID from list_resumes. (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": "generate_hot_words"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobNameYes
resumeIdNo
jobDescriptionNo

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', telling the agent its output is ephemeral and must be stored separately. It also discloses a real behavioral constraint not present in annotations: the call requires the user's sign-in with the interviews:write scope, which affects whether the call can succeed at all.

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 sentences, front-loaded with the purpose, then the persistence caveat, then the prerequisites. Dense and largely waste-free, with only minor redundancy in the 'come up in the interview and that speech recognition tends to get wrong' phrase.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-output-schema, read-only generator, the description covers purpose, non-persistence, follow-up tools and auth, which is most of what an agent needs. It never says what the call returns (presumably a list of term strings) nor gives any sense of volume or shape, which matters because there is no output schema to fall back on.

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 description coverage is 0%, so the description must carry the meaning, and it does map the three inputs ('role name, description and optional resume') and marks the resume as optional plus shows where to obtain it. However, it adds no detail on the 100/1000 character limits, on what happens when jobDescription is omitted, or on how jobName is used downstream, leaving real ambiguity for a zero-coverage schema.

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 verb and resource: have AI generate proper nouns that will appear in an interview and that speech recognition mis-transcribes, derived from a role name, description and optional resume. The scope is narrow and unmistakable, so an agent can tell it apart from the persistence and listing siblings without opening any schema.

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?

Explicitly states the tool only generates and that persistence must go through create_hot_word_library / update_hot_word_library or update_goal_hot_words, and points to list_resumes as the source of a resume ID. It stops short of saying when an agent should generate new words versus reuse library entries (e.g., via list_my_hot_words or get_goal_hot_words), so the exclusion set is incomplete but the primary routing is clear.

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