Skip to main content
Glama

match_goal_hot_words

为目标岗位自动匹配热词:按岗位信息(和可选简历)挑选官方词库并生成自定义热词,写回岗位。岗位已有热词时原样返回不覆盖(matched=false);force=true 时忽略已有热词重新匹配并覆盖。简历 ID 取自 list_resumes。(需要用户授权,范围 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

A4.2/5.0
Behavior5/5

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

Annotations only declare write/non-destructive/non-open-world; the description goes well beyond that by disclosing the write-back target, the non-overwriting default with its matched=false signal, the force-based overwrite path, and the required authorization scope interviews:write. This is exactly the operational context an agent needs before invoking a mutating tool. The overwrite on force=true is arguably in tension with destructiveHint=false, but since the content regenerated is derived hot-word data rather than user-authored records, I do not treat it as a genuine contradiction.

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?

The single paragraph is front-loaded with purpose, then behavior, then the resume-ID hint, then the auth requirement — a sensible ordering with no filler sentences. It is dense but every clause carries information; only the parenthetical auth note could be slightly tighter.

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?

With no output schema, the description usefully surfaces the one return signal that matters (matched=false) and covers the authorization prerequisite. For a three-parameter mutating tool with zero schema documentation, it leaves only minor gaps such as error behavior on unknown goalId or invalid resumeId.

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?

Schema coverage is 0%, so the description must carry the parameter burden, and it largely does: goalId is implicitly the target job whose hot words are matched, force is defined precisely as the overwrite switch, and resumeId is marked optional with its source (list_resumes). It does not spell out ID formats or what happens if a resumeId is invalid, so it is strong but not exhaustive.

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 opening clause names a specific verb and resource — automatically match hot words for a target job, selecting an official library and generating custom hot words — and adds that the result is written back to the job. That distinguishes it functionally from pure readers/generators in the sibling set. It stops short of naming a specific alternative (e.g. generate_hot_words or update_goal_hot_words), so sibling differentiation is implied rather than stated.

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 states the default branch (if the job already has hot words, return as-is with matched=false) and the override branch (force=true re-matches and overwrites), plus a concrete pointer that resume IDs come from list_resumes. What's missing is explicit routing guidance against the sibling hot-word tools — it never says when to prefer this over generate_hot_words or update_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