Skip to main content
Glama

AceRound AI Interview Copilot

follow_up_screen_question

Destructive

Ask a follow-up about the current screenshot question on the user's page (e.g. "another approach", "explain line 3"), same as typing a follow-up on the page; not possible while an answer is being written. Assessment follow-ups are billed by mode. Runs in the desktop assessment overlay when the user is in an assessment (it must have started); otherwise in screenshot solving on the live / mock interview page (the web page must be sharing the screen). Uses the user's minutes or credits or creates a payment; tell the user what it costs and get their agreement first. (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": {
      "message": "<message>"
    },
    "name": "follow_up_screen_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesThe follow-up

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well past the annotations by disclosing cost behavior (billed by mode, consumes minutes/credits or creates a payment), the required auth scope (interviews:write), the runtime environment switch, and a concurrency restriction. It also gives the agent an explicit consent obligation ('tell the user what it costs and get their agreement first'), which is exactly the kind of behavioral guidance annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, which is good, but the rest is a single dense run-on sentence stacking parentheticals for billing, environment, and auth. The information is valuable, yet the nested-clause structure makes it harder to parse than a short bulleted breakdown would be.

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?

Covers the things an agent most needs before calling: preconditions, environment, cost, and permission scope. The one gap is that it never hints at what the call returns or how the follow-up answer arrives, though with no output schema that omission is somewhat forgivable for a fire-and-observe interaction.

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 there is only one required field, so the baseline is already a 3. The description adds real meaning by illustrating the expected content of 'message' ('another approach', 'explain line 3'), clarifying that it is a short natural-language follow-up rather than an identifier or command.

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 ('Ask a follow-up about the current screenshot question on the user's page') and anchors it to a familiar analogue ('same as typing a follow-up on the page'), with two concrete examples. It implicitly separates itself from solve_screen_question by framing this as a follow-up to an existing question rather than a fresh solve, though no sibling is named 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 clear contextual conditions: it runs in the desktop assessment overlay when an assessment has started, otherwise in screenshot solving on the live/mock interview page with screen sharing active. It also states a hard exclusion ('not possible while an answer is being written'), but does not name an alternative tool for the cases where this one is unavailable.

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