Skip to main content
Glama
Sign In

Sweeprice

by com.sweeprice
OverviewDiscussionsAdmin

Set floor and ceiling price of a tracked product

set_product_price_bounds
DestructiveIdempotent

Sets the floor price and/or the ceiling price of one tracked product, the bounds no recommended price ever crosses. Pass null to clear a bound. At least one of the two must be given; the floor cannot exceed the ceiling.

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": {
      "productId": "<productId>"
    },
    "name": "set_product_price_bounds"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdYes
floorPriceNo
ceilingPriceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The description adds meaningful behavior beyond the annotations, including that null clears a bound, at least one bound is required, and the floor cannot exceed the ceiling. It also clarifies that these bounds constrain recommended prices, which is important context for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tightly written sentences with no wasted wording, and the core action is front-loaded before the validation constraints.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with annotations and no output schema, the description covers the key behavioral constraints and clearing semantics. The main minor gap is that the required productId parameter is not explained.

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 description coverage is 0%, so the description must carry parameter meaning. It explains the semantics of floorPrice and ceilingPrice, including null clearing and their relationship, but does not describe the required productId parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that it sets the floor and/or ceiling price of one tracked product and explains that these are bounds no recommended price crosses. The verb and resource are specific, though it does not differentiate itself from the sibling set_product_line_mode.

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

Usage Guidelines3/5

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

Usage is implied by the constraints: at least one bound must be given and null clears a bound. However, there is no explicit guidance on when to use this tool versus set_product_line_mode or other sibling tools.

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

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