Skip to main content
Glama

面灵AI 面试助手

run_prompt_trial

Read-only

提示词工作台试跑:用一段提示词按线上同一条链路、同一个模型当场作答一道题,查看效果。scene=interview 时填 question,可携带简历(list_resumes)、目标岗位与知识库(list_knowledge_bases);scene=exam 时选内置试题(get_prompt_presets 的 examPresets)或传题目截图 base64。prompt 为空串时按内置默认写法运行。不扣时长、不保存任何内容,但需要账户有可用时长;有频次限制。(需要用户授权,范围 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": {
      "scene": "<scene>"
    },
    "name": "run_prompt_trial"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNozh-CN
modeNoquick
sceneYes
goalIdNo
promptNo
questionNo
resumeIdNo
materialIdsNo
screenshotsNo
examPresetSlugNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive, and the description adds substantial context beyond them: no duration deducted, nothing persisted, but an available-duration prerequisite, rate limits, and an interviews:write authorization scope. These are exactly the operational facts an agent needs before invoking.

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?

Front-loaded with the core action, then scene branching, then behavioral caveats. Dense but every clause carries information; only the parenthetical authorization note feels slightly tacked on.

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?

For a 10-parameter tool with no output schema, the description covers the branching logic, input sources, and side-effect profile well. The remaining gap is the unexplained lang/mode/goalId parameters, which an agent would have to infer from the schema alone.

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?

With 0% schema description coverage the description must carry the load, and it explains scene, question, resumeId, materialIds (knowledge bases), screenshots (base64), examPresetSlug, and the empty-string prompt default. It leaves lang, mode, and goalId unexplained, so it is strong but not complete.

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?

States a specific verb and resource (trial-run a prompt to answer a question through the same online pipeline and model) and immediately branches by scene=interview vs scene=exam. An agent can distinguish this from siblings like answer_exam_now or rewrite_prompt without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use each mode and names the sibling tools that supply inputs (list_resumes, list_knowledge_bases, get_prompt_presets' examPresets). It also states the empty-prompt fallback, so the agent knows the tool still runs without a prompt.

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