Skip to main content
Glama

DealMonitor

set_target_price

Change the target price of an existing watch.

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": {
      "watch_id": "<watch_id>",
      "target_price": "<target_price>"
    },
    "name": "set_target_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
watch_idYes
target_priceYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it. It does not say whether the new target price overwrites an existing one, whether any alert or notification state is reset, whether the watch must be active, or what permissions are needed. The presence of an output schema covers return values, but the mutation's side effects remain undisclosed.

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?

A single short sentence with the mutation and its target front-loaded, and no wasted words. Its brevity is appropriate in structure but reflects under-specification rather than discipline.

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

Completeness2/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 annotations, the definition is too thin: the critical semantics of the price value (units, currency, constraints) and the effect of overwriting a target are absent. An agent could call it correctly on shape alone but could easily pass a wrong-scale or wrong-currency value.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters, so the description must compensate and largely fails to. It only echoes 'target price' and 'existing watch'; it adds no units or currency for target_price, no indication whether it is absolute or a percentage, and no meaning for watch_id beyond the name.

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 names a specific verb (change) and resource (target price of an existing watch), which cleanly separates it from read-oriented siblings like check_price, price_history, and list_watches. It stops short of explicitly naming which sibling to use instead for other price operations, so it is clear but not differentiating at the highest level.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus check_price or watch_price, no prerequisites beyond the implicit 'existing' watch, and no exclusions. The agent must infer that this is a mutation to be used after a watch has been created, with no guidance on ordering or alternatives.

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.

Resources