Skip to main content
Glama

get_goal_hot_words

Read-only

查看一个目标岗位当前生效的热词:绑定的热词库(ID、名称、是否自建)与自定义热词。(需要用户授权,范围 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 declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-structured information: the required authorization scope (interviews:read) and the shape of the returned content (bound libraries vs. custom hot words). It does not discuss pagination or limits, but for a single-scope read that is a minor gap.

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 compact sentence with the main payload front-loaded and an authorization note in a trailing parenthesis, which is efficient. The field list in parentheses is useful rather than padding.

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 one parameter, no output schema, and simple annotations, the description supplies what matters: what is returned and what auth scope is needed. The only meaningful omission is the semantics/format of goalId, which the description only gestures at.

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?

The single parameter goalId has 0% schema description coverage, so the description carries the burden; it does indicate the identifier refers to a target job position ('一个目标岗位'), which is the key semantic. It stops short of stating the ID format or where such an ID comes from, leaving a residual gap for an undocumented required parameter.

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 gives a specific verb (查看) and resource (热词) plus a clear scope qualifier ('当前生效' for a target position), and it even enumerates what is returned (bound libraries with ID/name/self-built flag, plus custom hot words). It does not explicitly name a contrasting sibling such as update_goal_hot_words or match_goal_hot_words, so differentiation is by implication only.

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 implied by '当前生效' and the read-oriented framing, but there is no explicit statement of when to choose this over update_goal_hot_words or match_goal_hot_words, nor any stated preconditions beyond authorization. An agent can infer it is the inspection step before an update, but must infer it.

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