Skip to main content
Glama

Dealectics deal verdict

Watch for a deal and e-mail the buyer

create_watch

Use when the person wants to be told when a good deal appears, and has agreed to receive e-mail. Sends them a confirmation link; nothing is watched until they open it, and you cannot confirm for them.

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": {
      "email": "<email>",
      "need": "<need>",
      "user_consented": "<user_consented>"
    },
    "name": "create_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYesWhat to watch for, in the person's words.
emailYesThe person's own address. They confirm the watch from that mailbox.
max_priceNoHard ceiling in euros. Offers above it are never sent.
user_consentedYesTrue only if the person asked for this watch and agreed to be e-mailed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / email / description
      Added value: +"The person's own address. They confirm the watch from that mailbox."
    • addedInput schema / properties / max_price / description
      Added value: +"Hard ceiling in euros. Offers above it are never sent."
    • addedInput schema / properties / need / description
      Added value: +"What to watch for, in the person's words."
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the two-step confirmation flow, that no watch is active until the link is opened, and that the assistant cannot complete confirmation for the user. These are important behavioral traits for a non-read-only, open-world tool that emails an external address.

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 the usage condition front-loaded and the confirmation caveat immediately following. Every sentence carries useful information without repetition.

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 mutating, externally visible tool with no output schema, the description covers the essential confirmation and consent behavior an agent must understand before calling it. It could say more about the immediate result of the call or failure cases, but the key operational caveat is present.

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 100%, so all four parameters are already documented in the input schema, including the email confirmation requirement, the person's own words for the need, and the hard price ceiling. The description adds little parameter-specific meaning beyond the schema.

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 frames the tool around setting up a deal watch: it sends a confirmation link, and nothing is watched until the recipient opens it. That distinguishes it from read or stop operations, though it does not explicitly say 'creates a watch' or name sibling alternatives.

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?

The opening sentence gives a clear when-to-use condition: the person wants deal notifications and has agreed to receive e-mail. It also states a critical constraint that the assistant cannot confirm on the person's behalf, but it does not explicitly say when not to use it or point to alternatives such as get_watch or stop_watch.

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