Skip to main content
Glama

AceRound AI Interview Copilot

run_prompt_trial

Read-only

Prompt studio trial run: answer one question with a given prompt through the same pipeline and model as production. For scene=interview give question, optionally with a resume (list_resumes), target role and knowledge bases (list_knowledge_bases); for scene=exam pick a built-in question (examPresets from get_prompt_presets) or pass screenshots as base64. An empty prompt runs the built-in default. Charges nothing and saves nothing, but the account must have time available; rate-limited. (Requires the user's sign-in with scope 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.2/5.0
Behavior5/5

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

Adds substantial context beyond the readOnly/non-destructive annotations: charges nothing, saves nothing, requires available account time, is rate-limited, and needs sign-in with the interviews:write 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-loads the core purpose, then branches by scene, then closes with cost/safety constraints. Dense but every clause carries information; the nested parentheticals make it slightly harder to scan than necessary.

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, no-output-schema tool this covers the essential call path and side-effect profile. Only the three unmentioned parameters (lang, mode, goalId) keep it from being fully complete.

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 across 10 params, the description carries the burden well: it explains scene, question, resumeId (via list_resumes), materialIds (knowledge bases), examPresetSlug (via get_prompt_presets), screenshots as base64, and prompt default behavior. It leaves lang, mode and goalId unexplained, which is the remaining gap.

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: 'answer one question with a given prompt through the same pipeline and model as production', framed as a trial run. That distinguishes it from the production answer tools (answer_exam_now, answer_live_interview_now) by implication, though it never names them explicitly.

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?

Gives concrete per-scene guidance: for scene=interview supply a question with optional resume, target role and knowledge bases; for scene=exam pick a built-in preset or pass screenshots. It also notes an empty prompt runs the built-in default. It stops short of explicit when-not-to-use or naming the production alternative.

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