Skip to main content
Glama

get_negotiation_playbook

Negotiation playbook for a previous scan: for each flagged clause, what to ask the vendor for, an acceptable fallback, your leverage, and the walk-away signal. Use this when procurement or legal needs to push back on a vendor's terms. Negotiation guidance, not legal advice.

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": {
      "scan_id": "<scan_id>"
    },
    "name": "get_negotiation_playbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
scan_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden, and it does disclose the scope constraint (requires a previous scan) and a meaningful caveat ('Negotiation guidance, not legal advice') that affects how output should be relayed. It does not state read-only/rate-limit behavior or what happens when scan_id is unknown, but the 'get_...playbook' framing makes the read-only nature evident.

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, front-loaded with the resource and its contents, then the usage trigger, then the disclaimer. Every sentence adds information an agent needs and none repeats the schema or title.

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 single-parameter retrieval tool with an output schema (so return values need not be explained) and no annotations, the description covers purpose, content, usage context, and a caveat. The only substantive gaps are failure behavior for a bad scan_id and whether the call has any quota cost, which siblings like check_quota suggest may matter.

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 0%, so scan_id is undocumented structurally; the phrase 'for a previous scan' does tie the parameter to an existing prior scan, adding real meaning. However, no format, example, or behavior for an invalid/unknown scan_id is given, so it only partially compensates for the coverage gap.

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

Purpose5/5

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

The description names the artifact precisely ('Negotiation playbook for a previous scan') and enumerates its per-clause contents: what to ask for, an acceptable fallback, leverage, and the walk-away signal. That is far more specific than 'get a playbook' and lets an agent distinguish it from report-style siblings such as get_scan_report.

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?

It gives an explicit trigger — 'Use this when procurement or legal needs to push back on a vendor's terms' — which tells the agent the situation that selects this tool. It stops short of naming an alternative or stating when not to use it (e.g. before a scan exists), so it is clear context rather than full routing guidance.

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.