Skip to main content
Glama
Sign In

Scrapewise

by ai.scrapewise
OverviewDiscussionsAdmin

scrapewise_get_matcher_run_estimate

Read-onlyIdempotent
        Tells what the NEXT run of the group costs and whether the wallet can start it, before you press Run
        (scrapewise_update_matcher_job with draft=false). Read-only; costs nothing; a Read key may call it.

        Every amount is a whole number of wallet units (the field names end in Micros; 1,000,000 = 1 euro) at the
        price the customer pays. A run reserves up to reserveMicros and charges only what it used: the rest comes
        back when the run ends.

        Args:
          - id (string, path, required): the group's id.
          - 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:
          sizeClass, worstServerType, customerPricePerHourMicros, perRowMicros, scopeRows (item rows the run would
          process), lines (tier server | rows | pictures with units, unitPriceMicros, maxMicros, typicalMicros),
          reserveMicros, typicalMicros, balanceMicros, reservedMicros, availableMicros, canStart, missingMicros,
          reasonCode (FLOW_RUN_SERVER_WALLET_LOW when the balance is too low) and chargeFrom (ISO time money starts
          from; null until it is set, and nothing is reserved or charged before it).

        Examples:
          - Use when: "what will the next run of group {id} cost?" or "can my wallet start this run?".
          - Don't use when: you want a finished run's charge -> scrapewise_get_matcher_history.

        Error Handling:
          - 404: no group with this id for this customer, or run costs are not switched on yet.
          - 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_matcher_run_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
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. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses that the call costs nothing, that a Read key may invoke it, and the reservation model (up to reserveMicros reserved, only usage charged, remainder returned when the run ends). It also documents chargeFrom semantics and the specific 404/409/401/500 failure modes, which annotations cannot convey.

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?

The critical constraint (cost of next run, wallet check) is front-loaded, and the Args/Returns/Examples/Error Handling structure makes it scannable. The Returns enumeration is long, but it is justified because no output schema exists; the heavy indentation is the only minor waste.

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 supplies the full return field list (reserveMicros, typicalMicros, balanceMicros, canStart, missingMicros, reasonCode, chargeFrom) plus error handling, so an agent knows both what it gets back and how to interpret a refusal. Nothing needed to call it correctly 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 only 50% (id has no schema description), but the description compensates by documenting both parameters: id as the group's id, and customerRef as an admin-only Take Over field that is required then and triggers 409 TAKE_OVER_ACTIVE without it. This adds real meaning beyond the schema, though the id description is minimal.

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 opening sentence names a specific verb and resource: it reports what the NEXT run of a group costs and whether the wallet can start it, and it explicitly contrasts with scrapewise_update_matcher_job with draft=false. An agent can distinguish this from scrapewise_get_matcher_history without opening either 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?

It gives explicit 'Use when' phrasings ("what will the next run of group {id} cost?", "can my wallet start this run?") and an explicit 'Don't use when' that routes to scrapewise_get_matcher_history for a finished run's charge. Both the positive and negative conditions are stated.

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

All Scrapewise 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