Skip to main content
Glama

scrapewise_get_match_evidence

Read-onlyIdempotent
        Lists the product pairs of the group's latest finished matching run, 50 per page, with the matcher's own
        stored fields for each pair, exactly as the matcher wrote them: its decision, basis, code and code kind, the
        gates that fired, the deciding step / rule, every match line with its own name, level, score and result, the
        signals and scores, and the review fields. Nothing is re-judged or renamed here. Read-only; costs nothing; a
        Read key may call it.

        Args:
          - id (string, path, required): the group's id.
          - page (integer, query, optional, default 0): the page, 50 pairs each.
          - bucket (string, query, optional, default all): matched | review | no | all (by the stored decision).
          - customerRef (string, query, optional): only for a Scrapewise admin key while the admin works in
            another customer's account (Take Over): the customerUniqueRef of that customer. Required then
            (409 TAKE_OVER_ACTIVE without it); leave it out otherwise.

        Returns:
          groupId, page, size (50), totalElements, totalPages and rows. Each row: pairId, link (the shop page, an
          http(s) address or null) and stored: the matcher's fields as stored, for example matchDecision,
          matchBasis, matchCode, matchCodeKind, gatesFired, decidedBy, matchLines, signals, signalCoverage,
          totalScore, eanVerdict, matcherEngine, masterRef, reviewVerdict, reviewMasterRef, sourceName. A field
          the matcher did not write is left out; a stored null is null; values the matcher adds later pass as
          they are. No group run yet: rows is empty.

        Examples:
          - Use when: "why did these products match?", "which matches rest on an EAN?", "show the review pairs".
          - Don't use when: you want what the next run costs -> scrapewise_get_matcher_run_estimate; the run's
            state -> scrapewise_get_matcher_config_status.

        Error Handling:
          - 400: page below 0, or an unknown bucket.
          - 404: no group with this id for this customer.
          - 409 TAKE_OVER_ACTIVE: this key's admin works in another customer's account — end Take Over or
            send customerRef=<that customer's ref>.
          - 401 Unauthorized; 500 INTERNAL.

[runtime hint] This tool returns JSON-as-text — its response shape is dynamic (per-scraper itemsConfig, file binary, etc.) so the MCP outputSchema is omitted. Do not rely on the presence of any specific field in the response; treat the result as a string-or-object blob and parse defensively.

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": {
      "id": "<id>"
    },
    "name": "scrapewise_get_match_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's id.
pageNothe page, 50 pairs each.
bucketNomatched | review | no | all (by the stored decision).
customerRefNoAdmin keys in Take Over only: the customerUniqueRef of the customer the admin works for. Required then; leave it out otherwise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / bucket / description
      Added value: +"matched | review | no | all (by the stored decision)."
    • addedInput schema / properties / id / description
      Added value: +"the group's id."
    • addedInput schema / properties / page / description
      Added value: +"the page, 50 pairs each."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), it discloses cost ('costs nothing'), auth scope ('a Read key may call it'), the pass-through guarantee ('Nothing is re-judged or renamed here'), empty-run behavior ('No group run yet: rows is empty'), and the Take Over / customerRef coupling. This is exactly the extra context annotations cannot carry.

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?

Well front-loaded and organized into Args / Returns / Examples / Error Handling, so scanning is easy. Some redundancy remains ('exactly as the matcher wrote them' immediately followed by 'Nothing is re-judged or renamed here') and the exhaustive field enumeration is long relative to its value.

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?

With no output schema, the description carries the return-shape burden and does so thoroughly: pagination envelope fields, per-row structure, omitted/null/sparse-field rules, and the error matrix. An agent has everything needed to call it and interpret the result, including the no-run edge case.

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 100%, so baseline would be 3; the description adds value by tying customerRef to a concrete failure mode (409 TAKE_OVER_ACTIVE) and restating the required/optional contract. It does not add much beyond the schema for page or bucket, but the customerRef consequence is genuinely useful.

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 opens with a specific verb and resource — 'Lists the product pairs of the group's latest finished matching run' — and pins down page size (50) and scope (latest finished run). It is clearly distinguishable from adjacent tools like scrapewise_get_matcher_run_estimate and scrapewise_get_matcher_config_status.

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

Usage Guidelines5/5

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

Explicit 'Use when' phrasings ('why did these products match?', 'which matches rest on an EAN?') and an explicit 'Don't use when' block that names two alternative tools and what they cover instead. Bucket semantics further route the caller (matched | review | no | all).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.