Skip to main content
Glama

match_goal_hot_words

Auto-match hotwords for a target role: pick official libraries and generate custom hotwords from the role (and optional resume), then save them to the role. If the role already has hotwords they are returned unchanged (matched=false); force=true re-matches and overwrites. 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": {
      "goalId": "<goalId>"
    },
    "name": "match_goal_hot_words"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo
goalIdYes
resumeIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The description carries substantial behavioral weight here: idempotent no-op semantics when hotwords exist (matched=false), the overwrite behavior of force=true, and the required 'interviews:write' scope. Those are real additions. However, the annotations already declare readOnlyHint=false and destructiveHint=false, and there is mild tension with 'overwrites' — the description should clarify that the overwrite replaces generated hotword sets rather than deleting user data, which it never resolves.

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 paragraph that front-loads the purpose and the core behavior before the parameter hints. The trailing parenthetical about sign-in scope is tacked on awkwardly, and the force/idempotency clauses could be split for scanability, but there is no filler.

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?

There is no output schema, and the description does volunteer the key return signal (unchanged results, matched=false), plus the auth scope and the idempotency contract. For a three-parameter, non-destructive mutation with no output schema, that covers what an agent needs to invoke it correctly, with only the goalId definition thin.

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

Parameters2/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 all three parameters. It explains force (re-match and overwrite) and resumeId (source: list_resumes, optional), but goalId is only obliquely referenced as 'the role' and never identified as the role/goal identifier that the whole operation is scoped to. Two of three parameters are covered, with the required one left least defined.

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 opens with a specific verb and resource: 'Auto-match hotwords for a target role', then spells out the mechanism (pick official libraries, generate custom hotwords, save to the role). That distinguishes it from a pure reader like get_goal_hot_words, though it never names a sibling explicitly, so the differentiation is inferred rather than declared.

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 gives a concrete when-to-use rule: if the role already has hotwords they come back unchanged, and force=true is the escape hatch to re-match. It also points to list_resumes for obtaining a resumeId. What it lacks is any exclusion guidance naming update_goal_hot_words or get_goal_hot_words as the manual/read alternatives.

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