get_board_imageRetrieve a PNG image of the full whiteboard—handwriting, sketches, and layout—to review freehand strokes and gain visual context in a system design interview.
A PNG picture of the whole board as the candidate sees it (handwriting, sketches, layout). Use when get_board mentions freehand strokes or you need visual context.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the useful facts that the payload is an image in the candidate's own view. It does not say whether the image is a current snapshot, its size, or whether repeated calls re-render, which are minor remaining gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences: the first defines the artifact, the second defines when to reach for it. Nothing redundant, and the key scoping fact (whole board, candidate's perspective) is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-argument tool with no output schema, the description adequately conveys the return medium and content. Only freshness/staleness of the snapshot is unaddressed, which is a small but real gap given the tool returns a visual state.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing the description needs to disambiguate; baseline applies. No parameter-related claims are made or needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States exactly what is returned: a PNG image of the whole board as the candidate sees it, including handwriting, sketches and layout. This clearly separates it from the text-oriented get_board sibling without opening either schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives two explicit triggers — get_board reports freehand strokes, or visual context is needed — and names the sibling it complements. An agent can decide between the text and image views from the description alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.