Skip to main content
Glama

get_saas_negotiation_playbook

Read-only

Use when a major SaaS contract is approaching renewal or auto-renewal risk. Returns timing strategy, leverage points, walk-away alternatives, and a complete negotiation script for any vendor. Example: Datadog renewal — initiate 90 days before, cite Grafana Cloud at 40% lower cost as walk-away, target 15-20% discount — Q4 close adds urgency leverage. Source: Stratalize procurement intelligence. $0.02 USDC per call.

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": {
      "vendor_name": "<vendor_name>"
    },
    "name": "get_saas_negotiation_playbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendor_nameYese.g. Salesforce, HubSpot, Slack
renewal_days_outNoDays until renewal
contract_value_annualNoCurrent ACV in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses the payable cost ($0.02 USDC per call) and the data source (Stratalize procurement intelligence), which materially affect an agent's decision to call it. The annotation openWorldHint=true is consistent with the claim that it works "for any vendor"; no contradictions present.

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?

Front-loaded with the usage trigger, then the return payload, then a concrete example and cost. The Datadog example is the longest element but earns its space by demonstrating the output shape; no sentence is pure filler.

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 no output schema, the description carries the burden of telling the agent what comes back, and it does so by listing the four deliverables. Cost, source, and scope are all covered; only the interaction with sibling playbooks is left unaddressed.

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 100%, so vendor_name, renewal_days_out, and contract_value_annual are already documented. The worked Datadog example illustrates how to reason about timing (90 days) and pricing targets but does not add semantics to the specific parameters beyond what the schema states. 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?

The description names a specific resource (a SaaS renewal negotiation playbook) and enumerates exactly what it returns: timing strategy, leverage points, walk-away alternatives, and a full negotiation script. It is clearly not a generic negotiation or market-intel tool, but it never explicitly contrasts itself with close siblings such as get_vendor_negotiation_intelligence or get_macro_playbook, so it stops short of a 5.

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?

"Use when a major SaaS contract is approaching renewal or auto-renewal risk" gives a concrete triggering condition an agent can match against a conversation. It does not state when NOT to use it or which sibling to prefer for adjacent cases, leaving that to inference.

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