Skip to main content
Glama

面灵AI 面试助手

list_hot_word_libraries

Read-only

列出可绑定到目标岗位的热词库:官方词库与用户自建词库(isOwn=true)的 ID 和名称。热词让语音识别准确识别专有名词。(需要用户授权,范围 interviews:read)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_hot_word_libraries"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds two things they do not: a required authorization scope (interviews:read) and the shape of the returned data (IDs and names only). That combination is useful context an agent would otherwise have to discover by failing a call.

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 short sentences, front-loaded with the resource and scope, followed by a one-line explanation of what hot words do and the auth requirement in parentheses. The middle sentence on speech recognition is domain context rather than invocation guidance, but it is brief enough to justify its place.

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

Completeness5/5

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

For a zero-parameter read tool with no output schema, the description supplies the result set definition, the returned fields (ID and name), and the required permission scope. Nothing needed to invoke it correctly is missing.

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?

The tool takes zero parameters, so the baseline is 4; there is no input surface for the description to clarify. The description does not introduce any phantom inputs or filter concepts that would confuse the caller.

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?

States a specific verb and resource ('列出...热词库') and scopes the result set to official libraries plus user-created ones (isOwn=true) that can be bound to a target position. This clearly separates it from create/update/delete/suggest siblings, though it does not explicitly distinguish itself from list_my_hot_words.

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?

The inclusion criteria (official + isOwn=true, bindable to a target position) imply the retrieval scenario, but there is no explicit when-to-use statement or routing to alternatives such as suggest_hot_word_libraries or list_my_hot_words. An agent can infer the use case but must decide alone between the listing tools.

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