Skip to main content
Glama

uplus_capture_question_image

Captures and saves a screenshot of a specific question block or full page, making diagram-based questions readable when the text alone is insufficient.

Instructions

Screenshot one question block and return it as an image.

Use for figure questions — a stem whose diagram/picture carries the part that makes the statement true or false (for example "以下模型是…" with a crypto diagram). The question text alone cannot be answered reliably, and the model cannot see an <img> that lives in the platform's rich text.

The tool opens the answer page, navigates to the question by its stem (same rule as filling), and captures that question's container — not just the viewport — so the whole figure is readable. It fills and submits nothing. Identify the question with order (the number shown on the page) or question_id. The result is the saved PNG path plus the image itself; answer the question after looking at it and pass the answer to uplus_answer_homework keyed by question_id.

output_path is optional and confined to the configured IO roots; by default the PNG goes under the report folder's question_images/. Set full_page=True when the figure sits outside the question block (for example a shared table above the questions).

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": {
      "task_id": "<task_id>",
      "course_id": "<course_id>"
    },
    "name": "uplus_capture_question_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderNo
task_idYes
course_idYes
full_pageNo
output_pathNo
question_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.8

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations at all, the description still discloses the important behaviors: it opens the answer page, navigates by stem, captures the question container, and crucially "fills and submits nothing" so the agent knows it is non-destructive. It also states the return value (saved PNG path plus the image), the default output location, that output_path is confined to configured IO roots, and the hand-off to uplus_answer_homework keyed by question_id.

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 rationale, then mechanics, then parameter notes in short paragraphs. A few clauses repeat the same idea ("the question text alone cannot be answered reliably" / "the model cannot see an <img>"), but nothing is wasted outright.

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 six-parameter tool with no annotations and no output schema, this is close to complete: it covers side effects, return shape, path defaults, and the follow-up workflow. It omits auth/session prerequisites and the meaning of task_id/course_id, so a small gap remains.

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 description coverage is 0%, so the description must carry parameter meaning and it does for four of six: order, question_id, output_path (default location and IO-root confinement) and full_page. task_id and course_id are left unexplained, and it is ambiguous whether order=0 means "unset" since order defaults to 0.

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 first sentence names a specific verb and resource ("Screenshot one question block and return it as an image") and the body scopes it precisely to a question container rather than the viewport. It is clearly distinguishable from generic browser screenshot siblings because it navigates to a specific question by stem/order/id.

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 an explicit when-to-use rule ("Use for figure questions — a stem whose diagram/picture carries the part that makes the statement true or false") plus the condition for the alternative mode (set full_page=True when the figure sits outside the question block). No named alternative tool or explicit when-not case, so not a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.