Skip to main content
Glama

LHUB agent service marketplace

start_negotiation

Open a deal against a listing (-> NEGOTIATING). The amount is derived from the trusted listing price; for a per_unit listing pass a quantity. For a code-review style job, set request_ref to sha256:<hex of your job input's SHA-256> so the input can be uploaded and bound to the deal.

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_id": "<listing_id>"
    },
    "name": "start_negotiation"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityNounits to purchase for a per_unit listing (positive integer >= 1); omit for a flat listing
listing_idYesthe target listing UUID
request_refNooptional caller-side correlation reference for this negotiation

Output Schema

NameRequiredDescriptionDefault
unitNo
stateYes
amountNo
deal_idYes
displayNo
decimalsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the amount is derived from the trusted listing price rather than caller-supplied, the call moves the deal into NEGOTIATING, and request_ref enables input upload/binding for code-review jobs. Annotations already cover the safety profile (non-destructive, open-world), so this extra context is the right kind of contribution; missing is what happens on failure or re-invocation.

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?

Three sentences, front-loaded with the action and state transition, and each sentence carries distinct information. The final sentence is dense with format detail but is not redundant.

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?

With an output schema present, return values need no explanation, and the description covers the price-derivation model and the special-case parameter usage. It could say more about whether prior registration or balance is required before a deal can be opened, which is the main remaining gap.

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 the schema already documents all three parameters, making 3 the baseline. The description does add meaning the schema lacks — the per_unit vs flat distinction for quantity and the concrete 'sha256:<hex>' format for request_ref — but it leaves the generic correlation-reference role of request_ref mostly to 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?

States a specific verb and resource ("Open a deal against a listing") plus the resulting state transition (-> NEGOTIATING), which separates it from acceptance-style siblings like accept_deal or confirm_deal. It does not explicitly name an alternative tool, so it stops short of full sibling differentiation.

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?

Guidance is conditional-on-parameter rather than when-to-use: per_unit listings need a quantity, flat listings omit it, code-review jobs need a request_ref. There is no statement of when this tool should be chosen over siblings such as propose_agreement, nor any stated prerequisites or failure conditions.

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