Skip to main content
Glama

set_price

Set the asking price for your own pixels (anyone may buy them at this price). Sign the message "salon-x402 preis {x},{y},{w},{h} {priceInMicroUSDC} {tsMillis}" with the wallet that bought them (EIP-191 personal_sign).

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": {
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>",
      "price_usdc": "<price_usdc>",
      "wallet": "<wallet>",
      "ts": "<ts>",
      "signature": "<signature>"
    },
    "name": "set_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
tsYes
widthYes
heightYes
walletYes
signatureYes
price_usdcYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does add genuine behavioral context: an authentication requirement (sign with the purchasing wallet) plus the exact signing scheme (EIP-191 personal_sign) and literal message template. It omits failure modes, whether an existing price is overwritten, and any rate/permission caveats, so it is strong but not complete.

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?

Two tight sentences: the action and its market effect come first, followed by the signing contract. The message template is dense but necessary; nothing is padding.

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

Completeness3/5

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

This is a state-changing, 8-required-parameter tool with no annotations and no output schema, so the description should do heavy lifting. It covers the authentication path well but leaves out return behavior, overwrite semantics, and any constraints on the region, leaving an agent with open questions before it can call confidently.

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% across 8 parameters, so the description must compensate and it partly does: it reveals that ts is milliseconds, that price_usdc is denominated in microUSDC, that wallet is the purchasing wallet, and that signature is an EIP-191 personal_sign over a fixed template. However x, y, width, and height are only echoed inside the message string without explaining that they form a pixel region, so half the parameters remain semantically thin.

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 first sentence states a specific verb and resource ('Set the asking price for your own pixels') and adds the consequence ('anyone may buy them at this price'), which clearly separates it from buy_pixel. It stops short of naming any sibling explicitly, but the purpose is unmistakable.

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 rather than stated: 'your own pixels' and 'the wallet that bought them' signal that the caller must already own the region, which is real guidance. There is no explicit when-to-use/when-not-to-use framing and no mention of what happens if a price already exists.

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.