Skip to main content
Glama

start_negotiation

Register a listing for price negotiation using the buyer's hard limit; no message is sent, and it returns the allowed offer range plus a suggested opening offer.

Instructions

Register a listing for negotiation with the buyer's hard price limit. Sends nothing yet. Returns the allowed offer range and a suggested opening offer.

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": {
      "listing": "<listing>",
      "max_price_eur": "<max_price_eur>"
    },
    "name": "start_negotiation"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoBuyer context, e.g. pickup city or arguments worth using
listingYesListing URL or ad id
max_price_eurYesThe most the buyer will pay. Never tell the seller.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 meaningful work: 'Sends nothing yet' explicitly rules out any seller-visible side effect, and it discloses the return payload (allowed offer range plus suggested opening offer). It does not cover persistence, repeat-call behavior, or whether registration can be overwritten, which keeps it short of a 5.

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?

Three short sentences, each earning its place: what it registers, what it does not do, and what it returns. The no-side-effect clarification is placed early, before the return description.

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?

Three well-documented parameters, no nested objects, and no output schema, so the description appropriately describes the return value itself. Only the preconditions and idempotency of registration are left unaddressed, minor for this tool's complexity.

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%, so all three parameters are already documented, including the 'Never tell the seller' warning on max_price_eur. The description reinforces the hard-limit nature of that price but adds no syntax, format, or interpretation guidance beyond the schema, so baseline 3 applies.

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?

Specific verb plus resource: 'Register a listing for negotiation with the buyer's hard price limit' tells the agent exactly what state is created. The verb distinguishes it from close_negotiation and get_negotiation without naming them, but no sibling is explicitly called out.

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?

'Sends nothing yet' signals this is a setup step preceding drafting/sending, which implies the position in the workflow. However, it never states prerequisites (must the listing be fetched first?), what to do if a negotiation already exists, or which sibling to call next.

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