Skip to main content
Glama
webscout-mcp

webscout-mcp

by wxs-lang

recovery_policy

Retrieve fetch recovery thresholds, marker sets, reason-to-action rules, and classification stages as a table with drift warnings, so you can explain request escalations or review policy without reading classifier source.

Instructions

Get the fetch recovery policy table: thresholds, marker sets, reason→action rules, and classification stages, as data.

This is the single source the recovery classifier is bound to (the modules import their thresholds from this table, enforced by identity tests). Returns the rendered markdown table plus any drift warnings found while assembling it. Read-only, zero-arg — use it to answer "why did this request escalate?" or to review the policy without reading the classifier source.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it declares read-only behavior, zero arguments, and that the response is a rendered markdown table plus drift warnings. It also discloses provenance (modules import thresholds from this table, enforced by identity tests), which builds trust in the data. Minor gaps remain — it doesn't say what a drift warning implies or whether the call can fail.

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?

The content is front-loaded: what it returns, then what it is, then what it returns structurally, then when to use it. The parenthetical about identity tests is slightly indulgent but earns its place by explaining why the table can be trusted as a single source. No filler sentences.

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

Completeness5/5

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

For a zero-param read tool with an output schema, the description covers purpose, contents, provenance, return shape, and use cases — everything an agent needs to decide to call it. No meaningful gaps remain.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly reinforces this by explicitly labeling the tool "zero-arg." There is nothing further to clarify about parameter meaning.

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 description names a specific verb and resource ("Get the fetch recovery policy table") and enumerates its contents: thresholds, marker sets, reason→action rules, and classification stages. An agent can tell this is a policy-introspection tool rather than any of the web_fetch/web_search siblings 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?

It gives concrete when-to-use triggers: answering "why did this request escalate?" or reviewing policy without reading classifier source. It also states the zero-arg/read-only condition. No alternative tool is named, but none of the listed siblings plausibly overlaps, so the guidance is sufficient without an exclusion clause.

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