Skip to main content
Glama

scrapewise_update_scraper_group_price_monitor_pick

Idempotent
        Pins ONE listing as ours under one pairing-column value, for the cases where the data
        cannot tell: several of our own rows carry the same value, so the comparison would
        otherwise have to guess which is the product we sell. A confidently wrong price on a
        pricing screen is worse than an empty cell, so the tool asks instead of guessing.

        Idempotent by key — answering again for the same key REPLACES the previous answer rather
        than accumulating, because a person can only mean one listing at a time.

        Both the key and the name travel in the BODY and never in the path. When the pairing
        column is a product title the key is arbitrary customer text containing `/`, `#`, `%` and
        spaces; even percent-encoded, a proxy or path matcher can decode `%2F` early and route the
        request elsewhere.

        Args:
          - id (string, path param, required): the group's MongoDB ObjectId.
          - body (GroupPickDTO, required): key (the pairing-column value exactly as scraped,
            1-512 chars) and name (product name of the listing that is ours, 1-512 chars).

        Returns:
          The group's full pick map after the write, same shape as GET .../picks.

        Examples:
          - Use when: "under EAN 4741243009332 the one we sell is 'Varikatus LEGEND 3x4m'".
          - Don't use when: the pairing column is simply the wrong column — fix that on
            PUT /group/{id}/price-monitor instead of pinning thousands of rows by hand.

        Error Handling:
          - 400 (CustomerError envelope) if no such group for this customer, or if the group
            already holds the maximum of 5000 picks (which means the pairing column is not
            identifying products).
          - 400 if key or name is blank or longer than 512 characters.
          - 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_update_scraper_group_price_monitor_pick"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's MongoDB ObjectId.
bodyYesNames which listing under a pairing-column value is the customer's own.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"the group's MongoDB ObjectId."
  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 (which already flag idempotentHint=true and destructiveHint=false), the description adds the key-based replace-not-accumulate semantics, the 5000-pick cap that signals a bad pairing column, the full 400/401/500 error envelope, and the return shape. The body-only routing rationale explains a non-obvious constraint that would otherwise lead an agent to build a path-based call.

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 purpose and rationale, then cleanly sectioned into Args, Returns, Examples, and Error Handling. It runs long with several explanatory paragraphs, but each section carries operational information rather than filler; the prose rationale paragraphs are the only slightly padded part.

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?

For a two-parameter mutation with no output schema, the description still states what comes back (the group's full pick map, same shape as GET .../picks) and enumerates failure modes and their meanings. Nothing an agent needs in order to call this correctly and interpret the result is missing.

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 the baseline is 3, but the description adds real meaning: `key` is the pairing-column value exactly as scraped and may be arbitrary customer text with `/`, `#`, `%`, and `name` is specifically the product name of the listing that is ours. It also tightens the bounds by saying blank or >512 characters is a 400, whereas the schema declares minLength 0.

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 names a specific verb and resource: pin ONE listing as ours under one pairing-column value, and it explains the exact ambiguity being resolved (multiple own rows sharing a value). It also positions itself against the sibling that fixes the pairing column (PUT /group/{id}/price-monitor), so an agent can tell it apart from the delete/list pick tools and from the column-setting tool 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?

There are explicit 'Use when' and 'Don't use when' entries with a concrete worked example (EAN 4741243009332 → 'Varikatus LEGEND 3x4m') and a stated alternative action for the mis-configured-column case. The idempotency note also tells the agent it may safely re-answer rather than needing to check first.

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.