Skip to main content
Glama
Sign In

Scraper Finder

by com.scraperfinder
OverviewDiscussionsAdmin

Find tools by output field

find_by_field
Read-onlyIdempotent

Catalogue tools whose published output schema includes the fields you need (e.g. ['email', 'phone'] or ['salary']), optionally for one website, cheapest first among equal matches.

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": {
      "fields": "<fields>"
    },
    "name": "find_by_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
fieldsYesField names, e.g. ['email', 'rating'].
websiteNoOptional website name or domain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavior: results are ranked "cheapest first among equal matches" and only tools with a *published* output schema are considered — details absent from the annotations.

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?

A single sentence that front-loads the core predicate and uses the examples and tie-break rule as compact modifiers. It is dense but every clause carries information; 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?

No output schema exists, but "catalogue tools" reasonably signals a ranked list of tool entries, and the ordering rule is stated. Minor gaps: the meaning of `limit` and what a "cheapest" ranking actually measures are left implicit.

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 67%, and the description compensates by explaining that `fields` is matched against published output schemas (with format examples) and that `website` limits to a single site or domain. The `limit` parameter and its default cap of 25 are not addressed anywhere, so one gap remains.

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 gives a specific verb and resource — cataloguing tools whose published output schema contains named fields — with concrete examples (['email','phone'], ['salary']). It is clear and distinct in substance from list_websites and which_tool, though it never explicitly contrasts itself with those siblings.

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?

"whose published output schema includes the fields you need" tells an agent the selecting condition and "optionally for one website" scopes it further. There are no exclusions or named alternatives, so it stops short of full when/when-not guidance.

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

All Scraper Finder 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