Skip to main content
Glama

list_negotiations

Read-only

List seller negotiations filtered by status, showing each last offer and next step so you can track active, agreed, declined, abandoned, or seller-stopped purchase discussions.

Instructions

All negotiations with status, last offer and the next step.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_negotiations"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds value by disclosing the return contents (status, last offer, next step), which matters because there is no output schema, but it says nothing about ordering, volume, truncation, or whether the collection is scoped to the caller's workspace.

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?

One short sentence with no filler, and the scope word 'All' plus the returned fields are front-loaded. It is efficient, though it is efficient at the cost of the missing detail noted elsewhere.

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?

For a simple read-only list tool with one optional parameter and no output schema, enumerating the returned fields is a reasonable substitute for an output schema. It still leaves the status filter and result-ordering/size behavior unexplained, which an agent needs in order to call it correctly.

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 the single optional 'status' parameter, and the description does not compensate: its use of the word 'status' refers to a returned field, not the filter, which can actively blur whether status narrows the list. The enum values themselves are self-explanatory in the schema, but the filter's behavior is undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase 'All negotiations with status, last offer and the next step' conveys that this returns a collection of negotiations along with the fields each record carries, and 'All' implicitly contrasts with the single-record sibling get_negotiation. However, it is a noun phrase with no explicit verb ('list'), and it never names or acknowledges get_negotiation, so the distinction is inferred rather than stated.

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 when-to-use guidance, no condition for choosing this over get_negotiation, and no note about prerequisites or typical workflows. The agent must guess that this is the overview/list entry point and get_negotiation is the drill-down.

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