Skip to main content
Glama

面灵AI 面试助手

get_prompt_presets

Read-only

提示词工作台:查看面试作答与笔试答题两套提示词的现状——当前生效的写法、用户已保存的整段自定义提示词、官方版本与是否有官方更新、各档内置风格,以及可用于试跑的内置试题。默认只返回概览与各段字数;传 show 返回指定一段的全文。(需要用户授权,范围 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_prompt_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo按哪门面试语言渲染;不传按用户已保存的面试语言
showNo返回哪一段全文:current 当前设置渲染的写法 / saved 用户已保存的 / official 官方版本 / style:<档位> 内置风格

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds context beyond that: the default returns only an overview with per-section word counts (not full text), and the call requires user authorization with scope interviews:read — useful preconditions an agent would otherwise not know.

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 scope is front-loaded (prompt workbench), the enumeration of returned state follows, and the default/show distinction plus auth scope close it out. It is dense and somewhat run-on in a single block, but no sentence is wasted.

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, so the description carries the burden of describing returns — and it does, distinguishing the overview payload from the single-section full-text payload. With only two optional parameters, full annotation coverage, and explicit auth scope, an agent has what it needs to call this correctly; only explicit sibling routing 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?

Schema coverage is 100% and both enums are documented, so the baseline is 3. The description still adds value by explaining the default behavior when show is omitted (overview plus word counts) and that show returns the full text of exactly one section, which the schema does not state.

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 names the resource (prompt presets/workbench) and enumerates exactly what is inspected: current effective wording, saved custom prompt, official version plus update availability, per-tier built-in styles, and built-in exam questions available for trial runs — for both the interview and exam prompt sets. This is far more specific than the sibling names (rewrite_prompt, save_custom_prompt, run_prompt_trial) and makes clear this is the read/inspect counterpart.

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 rather than stated: it is clearly the inspection tool for prompt state, and the default-vs-show behavior is spelled out, but the description never explicitly says when to use this instead of rewrite_prompt, save_custom_prompt, or run_prompt_trial. No exclusions or routing sentence is present.

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