Skip to main content
Glama
Sign In
Theseus

Theseus

by ywapom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

screenshot

Capture the visible browser window and return the saved image's absolute path; enable full_page to save the entire page for review.

Instructions

Save a screenshot of the visible window and return its absolute path (open it to view). full_page=true takes the whole page, which on a long site is too tall to read.

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

Input Schema

NameRequiredDescriptionDefault
full_pageNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the full burden. It usefully discloses that the tool writes a file and returns a path the agent must open, and warns about the readability tradeoff of full-page capture, but says nothing about side effects on the page, file location, naming, format, or persistence.

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

Conciseness5/5

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

Two short sentences, zero filler, with the core behavior and return value front-loaded before the parameter caveat. Every clause earns its place.

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 single-parameter capture tool with an output schema already covering the return shape, this is nearly sufficient: the agent knows what is captured, what comes back, and how to consume it. Only the file-writing side effects and viewport context are left unstated.

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 0% — the sole parameter is documented only as "Full Page" with a boolean default. The description compensates well by explaining that full_page captures the entire page and that the result may be too tall to read on long sites, which is genuine semantic value beyond the schema.

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 ("Save a screenshot of the visible window") plus the return value ("absolute path"), which clearly separates it from text-oriented siblings like read_page or inspect_error. It never explicitly contrasts itself with those siblings, so it stops just short of the top mark.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: "open it to view" hints at the follow-up workflow, and "full_page=true ... on a long site is too tall to read" guides when to avoid the flag. There is no statement of when to prefer this over read_page or when a screenshot is unnecessary.

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

Deploy Server

Other Tools