SnoopScan

Check research progress

researchStatus

Read-onlyIdempotent

Check a research job: its status, recent progress and, once done, the report.

While it runs this lists the latest steps (searches, pages read, notes). When
it is done the full report is returned with its numbered sources. A report
marked partial stopped early and covers what was read before then.

Needs a free SnoopScan key.

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": {
      "jobId": "<jobId>"
    },
    "name": "researchStatus"
  }
}

Input Schema

Name	Required	Description	Default
`jobId`	Yes
`maxChars`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is lower. The description adds real value on top: it discloses what is returned in each job state and explains the 'partial' report semantics (stopped early, covers what was read), plus the auth requirement for a SnoopScan key. It omits polling cadence and whether repeated calls consume quota.

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 state-dependent return behavior is front-loaded and the partial-report caveat is a single efficient sentence. The trailing 'Needs a free SnoopScan key.' is somewhat orphaned as a standalone fragment but carries genuinely useful prerequisite information.

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?

An output schema exists, so return values needn't be spelled out, and the description still usefully covers the three job states. However, for a polling tool the missing pieces — how to obtain the jobId, and what maxChars actually caps — leave the agent without enough to invoke it correctly in edge cases.

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%, so the description must compensate, and it does not. Neither parameter is mentioned: 'jobId' is never explained (where it comes from), and 'maxChars' (default 30000) is especially ambiguous — whether it truncates the report, the progress list, or both is left entirely to guesswork.

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?

The description opens with a specific verb and resource — 'Check a research job' — and enumerates what is returned (status, recent progress, report). It is clearly distinct from the sibling 'research' tool, though it never names that sibling or states the relationship explicitly.

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 through state descriptions: 'while it runs' versus 'when it is done'. There is no explicit instruction such as 'call after research returns a jobId' or guidance on how often to poll, so the agent must infer the workflow from the sibling names.

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

All SnoopScan tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.