Skip to main content
Glama

Stratalize Intelligence

Get Saas Negotiation Playbook

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. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description adds genuinely new behavioral detail the annotations cannot convey: a per-call price of $0.02 USDC and the upstream source (Stratalize procurement intelligence), which matters for cost-aware agents.

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 trigger condition is front-loaded in the first clause, followed immediately by return contents, then supporting example and provenance. It reads as one dense but well-ordered paragraph; the example is long yet does illustrative work rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 must describe return values and does so concretely. It also discloses cost and data source, so an agent knows both what it gets and what it spends — nothing needed to call this correctly is missing.

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 all three parameters (vendor_name, renewal_days_out, contract_value_annual) are already documented. The Datadog example implicitly shows how the parameters are populated, but no additional format or edge-case semantics are added, so the baseline of 3 applies.

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 states a specific verb (returns a playbook) and enumerates concrete contents: timing strategy, leverage points, walk-away alternatives, and a negotiation script. The scoping phrase 'for any vendor' plus the Datadog example make the resource and its bounds unambiguous, distinguishing it from vendor-specific intelligence tools.

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 condition ('when a major SaaS contract is approaching renewal or auto-renewal risk') and reinforces it with a worked example of initiating 90 days before renewal. No exclusion or named alternative is provided, so it stops short of full when-not 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.

Resources