Skip to main content
Glama

面灵AI 面试助手

get_settings

Read-only

查看用户保存在云端的个性化设置:面试高级配置(面试语言、翻译语言、回答风格、默认挂载的知识库、面试复盘、联网搜索等)、笔试答题定制(答题语言、编程语言、代码风格、代码模式、补充要求、常驻快捷指令)与桌面客户端设置(快捷键、浮窗样式、档位、自动回答等)。自定义提示词只给字数,全文用 get_prompt_presets 查看。(需要用户授权,范围 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": "get_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, openWorldHint=false and destructiveHint=false, so the safety profile is known. Beyond that, the description adds two non-obvious behaviors: the call requires user authorization with scope interviews:read, and prompt bodies are deliberately truncated to a character count rather than returned in full.

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?

Purpose is front-loaded in the opening clause, followed by grouped field enumerations, then the truncation caveat and the auth-scope note. The enumeration of settings fields is long but each item is concrete; the only mild waste is the trailing '等' fillers that widen scope without adding precision.

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?

With no parameters and no output schema, the description must do the work of describing return contents, and it does so by listing the three settings categories and their fields. The authorization requirement and the prompt-truncation behavior close the remaining gaps an agent would otherwise discover only at call time.

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 schema carries no semantic burden and the baseline of 4 applies. The description correctly adds nothing about arguments and instead spends its words on what comes back.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb '查看' (view) and names the resource, the user's cloud-saved personalized settings, and then enumerates the three concrete groups returned (interview advanced config, written-exam customization, desktop client settings). It also states a scope boundary: custom prompt text is only summarized by character count here and must be fetched via get_prompt_presets.

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 explicitly routes the agent to get_prompt_presets for full prompt text, which is clear alternative guidance for the one overlapping case. It does not say when to call this versus write-side siblings such as update_client_settings or the other get_* account tools, but the read-only retrieval intent is unambiguous.

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