Skip to main content
Glama

pull_remote_screenshots

Fetches new PNG screenshots from a remote machine over SCP and adds them to the screenshot log, requiring SSH key-based authentication with no password prompt.

Instructions

Fetch new PNG screenshots from another machine over SCP (e.g. a Windows laptop where Win+PrtScn saves to Pictures\Screenshots) and add them to the log. Requires an SSH server on that machine and key-based auth (no password prompt).

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": {
      "host": "<host>",
      "user": "<user>"
    },
    "name": "pull_remote_screenshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
userYes
prefixNoremote
remote_dirNoPictures/Screenshots

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose key prerequisites: an SSH server on the target and key-based auth with no password prompt. It does not say what happens on auth failure, whether remote files are deleted or deduplicated, or what 'add them to the log' produces, leaving meaningful behavioral gaps for a network/mutation tool.

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 tight sentences with zero filler; the action and its prerequisites are front-loaded in that order.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the operational prerequisites well, but for a four-parameter tool with no annotations and no output schema, the description should explain the prefix and user parameters and at least hint at the result of the pull. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters. The description only indirectly gestures at host ('another machine') and remote_dir (the Pictures\Screenshots example); it says nothing about 'user' or 'prefix', so half the parameters remain unexplained in both schema and description.

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 specific verb (fetch/pull), resource (PNG screenshots), transport (SCP), and outcome (add them to the log), plus a concrete example source machine. An agent can distinguish this from save_screenshot or list_screenshots without opening the schema.

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 a clear usage context: pulling from another machine that already has screenshots saved locally, with a concrete example (Windows laptop, Win+PrtScn). It does not explicitly exclude alternatives or say when to prefer save_screenshot/list_screenshots instead, so it stops short of full routing guidance.

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