Skip to main content
Glama

Start a negotiation

initiate_negotiation

Start a new contract negotiation. Returns a negotiation token for the respondent to join. A2A_ contract types have a weekly limit on new negotiations: 5 per contract type, or 300 a week in total for an account holding credits. Making contracts, starting and joining negotiations and counter-proposals are limited to 100 requests an hour per customer; all calls together, to 1,000 an hour.

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": {
      "playbookId": "<playbookId>",
      "dealName": "<dealName>",
      "initiatorEmail": "<initiatorEmail>"
    },
    "name": "initiate_negotiation"
  }
}

Input Schema

NameRequiredDescriptionDefault
dealNameYesHuman-readable deal name
playbookIdYesID of your playbook
initiatorEmailYes
respondentEmailNo
initiatorCompanyNo
respondentCompanyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

The annotations only declare readOnlyHint=false and openWorldHint=false; the description goes well beyond that by disclosing concrete quota behavior: weekly caps (5 per contract type, 300 per account) on A2A contract types and hourly limits (100/hour for negotiation actions, 1,000/hour overall). It also states the return value, a negotiation token. It stops short of saying whether a negotiation can be cancelled or whether credits are consumed at creation.

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?

The purpose and return value are front-loaded in the first two sentences, with quota details pushed to the back. The rate-limit sentence is dense but every clause carries useful operational information; no filler.

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?

There is no output schema, and the description compensates by naming the returned token. However, for a six-parameter mutation that initiates a multi-party flow, the definition leaves optional fields (respondentEmail, companies) and their effects unexplained, and says nothing about what happens if a required contact is missing.

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 only 33%, so the description carries the burden of clarifying six parameters, yet it explains none of them. playbookId, initiatorEmail, the optional respondentEmail, and the two company fields get no meaning from the prose beyond the implicit mention of a 'respondent'.

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 opens with a specific verb and resource ('Start a new contract negotiation') and adds the concrete effect ('Returns a negotiation token for the respondent to join'). This makes it distinguishable from the sibling join_negotiation implicitly (start vs. join), though the alternative is never named.

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?

Usage is only implied by the phrase 'Start a new contract negotiation' and by the mention that the token is for the respondent to join, which sketches the workflow. There is no explicit when-to-use or when-not guidance, no prerequisites, and no named alternative such as join_negotiation or generate_contract.

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.