Scout MCP

cache

List a site's URLs once, then download filtered pages into Scout's saved copy in the background for reuse in reads and recipe runs.

Instructions

Cached mode, for pulling a lot from one site: list it once (filter narrows the urls) and download every page once into Scout's copy, in the background, at the host's pace. source='archive' downloads from the Wayback Machine with no request to the site; 'live' from the site; 'auto' live, with the archive where the site walls Scout. The copy is kept days; reads and recipe runs with cached=true use only it. action=status follows the job; action=stop ends it.

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": {
      "url": "<url>"
    },
    "name": "cache"
  }
}

Input Schema

Name	Required	Default
`url`	Yes
`days`	No
`action`	No	start
`filter`	No
`source`	No	auto
`max_pages`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Oct 19, 2026

TDQS

A4.1/5.0

Behavior4/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 well: it discloses background execution, pacing at the host's pace, retention for `days`, that reads/recipe runs with cached=true use only the copy, and that archive source makes no request to the site. It does not describe failure handling or what happens if a job is re-started.

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?

Three dense sentences, front-loaded with the scenario and the core behavior, with each clause carrying parameter or behavioral meaning. No filler.

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 6-parameter, no-annotation, no-output-schema job-control tool, this covers purpose, mode selection, retention, and lifecycle actions. The omission of max_pages semantics and any job-failure/status-return detail are the only remaining gaps.

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%, so the description must compensate and largely does: it explains source values (archive/live/auto), the meaning of days (copy retention), filter (narrows the urls), and action (status/stop). Only max_pages and the url parameter are left without any semantic explanation.

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+resource ('download every page once into Scout's copy') and the scenario it serves ('pulling a lot from one site'). It is clear what the tool does, though it does not name or differentiate itself against any of the many sibling tools.

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 when-to-use trigger ('for pulling a lot from one site') and describes the source selection trade-off (archive = no request to the site, auto = live with archive fallback). It never names an alternative sibling tool or an explicit when-not-to-use condition.

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

Deploy Server