Skip to main content
Glama

面灵AI 面试助手

solve_screen_question

Destructive

让用户正在运行的页面立即截取用户屏幕并解题,与按「截图答题」按钮 / 快捷键相同;按当前档位与页数扣费,答案显示在用户的页面上。AI 助理不需要也无法提供图片。执行端:用户正在进行笔试时为桌面客户端的笔试浮窗(需已开始本场笔试);否则为进行中的实时面试 / 模拟面试页面里的截图答题(网页端需已共享屏幕)。会消耗用户的时长、次数或产生付款,执行前向用户说明扣费内容并取得同意。(需要用户授权,范围 interviews:write)

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": "solve_screen_question"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: it charges against the user's current tier and page count, consumes time/quota or creates a payment, requires explaining the charge and obtaining consent first, and requires the interviews:write authorization scope. This is exactly the kind of side-effect disclosure destructiveHint implies.

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 action and its button equivalence, then layers preconditions, billing, and auth. The content is dense but every clause carries operational weight; a couple of parenthetical precondition clauses could be tightened.

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, high-consequence action with no output schema, the description covers trigger conditions, execution environment, billing, consent, auth scope, and where the answer appears — nothing an agent needs to call it safely 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 no parameters, so the baseline is 4; the description usefully clarifies that the agent neither needs nor can supply an image, removing the main ambiguity an agent might have about how to invoke it.

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 concrete verb and resource: immediately capture the user's screen on the currently running page and solve the question, equivalent to the 'screenshot answer' button/shortcut. It also tells the agent it supplies no image itself, which cleanly separates it from anything image-based.

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 explicit preconditions: the desktop exam floating window when a written exam has started, otherwise the screenshot-answering flow inside an ongoing live/mock interview page with screen sharing active. It does not name a sibling (e.g. follow_up_screen_question) as the alternative for follow-ups, so routing guidance is strong but not exhaustive.

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