Skip to main content
Glama

scrapewise_get_column_quality

Read-onlyIdempotent
        Counts how many products share an ID value in a column, so you can tell whether a column can be used as
        the group's ID column before a match run spends an hour on it. The ID column is what the matcher tells
        two products apart by: when two products carry the same value, saved decisions and kept matches cannot be
        told apart, and a run can be stopped by its own check for exactly that reason.

        Read only. It costs nothing, changes nothing and starts no run; a Read key may call it. Counts only, never
        a product's own values. Counts are computed over the trimmed, lower-cased value, which is what the matcher
        itself compares, so `duplicated` is what would really collide.

        Args:
          - id (string, path, required): the group's id.
          - body (required): {entries: [{jobId, column}]} - the main list's run and each connected shop's run in
            one call, at most 512 entries. jobId values come from scrapewise_get_matcher_scope_jobs or
            scrapewise_get_matcher_job (the saved scope).

        Returns:
          A bare JSON array of {jobId, column, total, empty, distinct, duplicated, tooLarge}. `total` = products
          in that run, `empty` = products with no value, `distinct` = different values, `duplicated` = products
          whose value another product also has. A column with duplicated 0 and a low `empty` is one you can use.
          tooLarge=true with null counts = that run is over the 500,000-row cap and was not counted; read the last
          run's own numbers from scrapewise_get_matcher_history instead.
          An entry is LEFT OUT of the array when its jobId is unknown or belongs to another customer, or when the
          column cannot be checked. The answer can even be empty for a whole group, because a scraper that
          declares no columns of its own offers none here. A missing entry never means "the column is fine": it
          means this call could say nothing about it.

        Examples:
          - Use when: "is the EAN column unique in group {id}?" before saving it as the ID column.
          - Use when: a run was stopped because products share an ID value, and you need to say which column to
            use instead.
          - Don't use when: you want the match result itself -> scrapewise_get_matched_data; or the reason a run
            was stopped -> scrapewise_get_matcher_history.

        Error Handling:
          - 400 (CustomerError): no group with this id for this customer, or more than 512 entries. Nothing was
            counted.
          - 429: too many uncounted checks for this customer in one minute, or too many running at once. Wait a
            minute and ask again with the same body; a repeat of the same question is served from the cache and
            costs nothing.
          - 402 without the text-matching feature; 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>",
      "body": "<body>"
    },
    "name": "scrapewise_get_column_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's id.
bodyYes{entries: [{jobId, column}]} - the main list's run and each connected shop's run in one call, at most 512 entries. jobId values come from scrapewise_get_matcher_scope_jobs or scrapewise_get_matcher_job (the saved scope).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / body / description
      Added value: +"{entries: [{jobId, column}]} - the main list's run and each connected shop's run in one call, at most 512 entries. jobId values come from scrapewise_get_matcher_scope_jobs or scrapewise_get_matcher_job (the saved scope)."
    • addedInput schema / properties / id / description
      Added value: +"the group's id."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial context: no cost, Read-key authorization, no run started, comparison performed on trimmed lower-cased values so `duplicated` reflects real collisions, a 500,000-row cap flagged by tooLarge with null counts, left-out entries for unknown/foreign jobIds or uncheckable columns, and 400/429/402 semantics including caching of repeated identical bodies.

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: purpose and rationale first, then Args, Returns, Examples, and Error Handling in labeled blocks that are easy to scan. Slight redundancy exists in the behavioral preamble ('costs nothing, changes nothing and starts no run' plus 'Read only'), but nearly every line carries actionable information given the missing output schema.

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 and a nested-object input, the description compensates fully: it enumerates every returned field (total, empty, distinct, duplicated, tooLarge), interprets them into a decision rule, and warns that a missing entry must never be read as a passing column. Error codes and the caching behavior of retries round out what an agent needs to call it safely.

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 coverage is 100% and the schema already documents both `id` and the nested entries array including the 512-entry cap and jobId provenance, so the description's Args block largely restates it. It adds no new per-parameter syntax or format detail, so baseline 3 applies; its richer content is behavioral rather than parameter-level.

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: it counts how many products share an ID value in a column, and states the decision the count supports (whether a column can serve as the group's ID column). It also explains the underlying matcher semantics (saved decisions and kept matches collide on equal values), which lets an agent distinguish it from sibling status/history tools without opening a schema.

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' cases (checking EAN uniqueness before saving an ID column; diagnosing a run stopped for duplicate IDs) and explicit 'Don't use when' routing to scrapewise_get_matched_data for results and scrapewise_get_matcher_history for the stop reason. Prerequisite jobId provenance is also named via scrapewise_get_matcher_scope_jobs / scrapewise_get_matcher_job.

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.