Skip to main content
Glama

AceRound AI Interview Copilot

get_goal_hot_words

Read-only

Read the hotwords in effect for a target role: bound libraries (ID, name, whether the user’s own) and custom hotwords. (Requires the user's sign-in with scope interviews:read.)

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": {
      "goalId": "<goalId>"
    },
    "name": "get_goal_hot_words"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), so the description's job is to add context — and it does, by disclosing the required sign-in scope (interviews:read) and describing the shape of the returned data. It stops short of explaining behavior when the goal has no bound libraries or how missing permissions surface as errors.

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?

One front-loaded sentence plus a short parenthetical for the auth requirement — no filler. The return-value enumeration is dense but earns its place by telling the agent what to expect.

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 single-parameter read tool with no output schema, the description covers purpose, return contents, and the auth prerequisite, which is most of what an agent needs. The remaining gap is error/empty-state behavior and goalId provenance, which are minor for a read-only lookup.

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% for the single goalId parameter, so the description must carry the load. Saying the hotwords apply to a "target role" gives goalId semantic meaning (it identifies the role/goal), but it never states the expected format, where the ID comes from, or what happens with an invalid ID.

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 pairs a specific verb ("Read") with a precise resource ("hotwords in effect for a target role") and even enumerates what the result contains: bound libraries with ID, name, and ownership flag, plus custom hotwords. It implicitly separates itself from sibling listers such as list_my_hot_words by scoping results to a target role, but it never names an alternative outright.

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?

Usage is only implied: an agent can infer this is the tool for inspecting the effective hotword set for a given role, and the sign-in/scope note signals a prerequisite. There is no explicit when-to-use vs. when-not guidance and no named alternative for the closely related list_my_hot_words or match_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