Skip to main content
Glama

scrapewise_update_scraper_group_currency

Idempotent
        Sets the group's Analytics-dashboard display currency. When set, the dashboard converts
        every price in the group to this ISO 4217 currency before showing or comparing it; a row
        already scraped in this currency is shown unconverted. displayCurrency=null clears the
        preference (each row shown in whatever currency it was scraped in, unconverted).

        Args:
          - id (string, path param, required): the group's MongoDB ObjectId.
          - body (GroupCurrencyDTO, required): displayCurrency — an ISO 4217 code (e.g. "EUR",
            "SEK"), or null to clear.

        Returns:
          The updated GroupDTO (carrying displayCurrency).

        Examples:
          - Use when: "show group {id}'s dashboard in euros" → displayCurrency="EUR"
          - Use when: "stop converting prices in group {id}" → displayCurrency=null

        Error Handling:
          - 400 (CustomerError envelope) if no group with the given id exists for this customer.
          - 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_currency"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's MongoDB ObjectId.
bodyYesdisplayCurrency — an ISO 4217 code (e.g. "EUR", "SEK"), or null to clear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / body / description
      Added value: +"displayCurrency — an ISO 4217 code (e.g. \"EUR\", \"SEK\"), or null to clear."
    • addedInput schema / properties / id / description
      Added value: +"the group's MongoDB ObjectId."
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare idempotent=true and destructive=false, and the description adds substantial context beyond them: conversion happens at display time only, rows already in the target currency are shown unconverted, null clears the preference and reverts to unconverted per-row display, and the tool returns the updated GroupDTO. It also enumerates failure modes (400 when the group id does not exist for this customer, 401, 500), which is real behavioral information an agent needs.

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?

Core behavior is front-loaded in the first sentence, and the Args/Returns/Examples/Error Handling blocks make scanning easy. Some redundancy exists — the Args block echoes the schema's own descriptions — but nothing is padded with filler.

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 covers return value (updated GroupDTO), error envelopes, and the null-clearing semantics. The runtime hint about dynamic JSON-as-text responses further removes ambiguity, so an agent has everything needed to call it correctly.

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 states that displayCurrency is an ISO 4217 code or null to clear, so the Args block largely restates structured data. The description does add the semantic consequence of the value (per-row conversion behavior), but the parameter-level detail itself adds little beyond the schema, matching the baseline 3.

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?

Opens with a specific verb and resource: 'Sets the group's Analytics-dashboard display currency,' which is distinct from the many other group-update siblings (category, retention, schedule, price monitor). It immediately explains the effect — converting every price in the group to the given ISO 4217 currency for display and comparison — so the agent knows exactly what changes.

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?

Provides explicit 'Use when' examples in both directions: setting a currency ("show group {id}'s dashboard in euros" → "EUR") and clearing it ("stop converting prices" → null). It does not name alternative tools or state when not to use it, but the resource is unambiguous enough that routing is clear.

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.