Skip to main content
Glama

SnoopScan

by com.snoopscan
OverviewDiscussionsAdmin

Extract structured data

extract
Read-onlyIdempotent

Extract structured data from one or more pages according to a JSON schema.

The output is validated against the schema — if a page does not contain the
required fields, that page returns an error rather than invented values.
An error for a page means the required fields are not on it.

Needs a free SnoopScan key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYes
promptNo
schemaYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, and the description usefully adds that output is validated against the schema and that a page without required fields returns an error rather than invented values. It also discloses the 'free SnoopScan key' auth requirement, adding real context beyond structured fields.

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?

Front-loaded with the core action, then the validation/error contract, then the credential requirement. The content is tight and every sentence carries weight, though the trailing key requirement reads slightly as an afterthought.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. The description covers the main behavior and error semantics well; the only omission is the optional 'prompt' parameter's role.

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

Parameters3/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 carry the burden. It explains the schema param (a JSON schema to validate against) and the urls param ('one or more pages'), but the optional 'prompt' parameter is never mentioned, leaving a gap.

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 (extract), resource (structured data from one or more pages), and mechanism (per a JSON schema), so the operation is unambiguous. However, it never distinguishes itself from close siblings like parse, scrape, or batchScrape, leaving the agent to infer the boundary.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance and no named alternative, despite several overlapping siblings (parse, scrape, batchScrape). The only implied usage is that a JSON schema and pages are supplied; the agent gets no help choosing this over neighbors.

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

All SnoopScan toolsInspect
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.

Resources