Skip to main content
Glama

get_vendor_negotiation_intelligence

Read-only

Use when preparing to renew or renegotiate a SaaS contract. Returns typical discount percentage, best negotiation windows, leverage points, auto-renewal risk flags, and a negotiation script for any vendor. Example: Salesforce renewals average 12-18% discount when initiated 90 days before renewal with multi-year commit — Q4 close urgency adds 5-8% additional leverage. Source: Stratalize procurement intelligence composite. $0.10 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_vendor_negotiation_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendor_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, open-world behavior, and the description adds genuinely new context: the data source (Stratalize procurement intelligence composite) and the per-call price of $0.10 USDC, plus a sample output showing the granularity of returned figures. It does not discuss coverage limits, confidence levels, or what happens for vendors with no data, which is the main remaining gap.

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?

It is front-loaded with the usage trigger, then the return payload, then an illustrative example, source, and price. Every element earns its place, though the Salesforce example is somewhat long relative to the rest.

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 describing returns and does so by enumerating the five output categories. Combined with cost and source disclosure, an agent has enough to decide and invoke correctly; only edge-case behavior for unknown vendors is unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single vendor_name string, but the description compensates by stating the tool works "for any vendor" and illustrating with a named vendor (Salesforce), making the expected free-form vendor-name input clear. No format constraints (ticker vs. legal entity name) are specified.

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 concrete resource (vendor negotiation intelligence) and enumerates exactly what comes back: discount percentage, negotiation windows, leverage points, auto-renewal risk flags, and a script. It is clearly scoped to SaaS contract renewal/renegotiation, which separates it from generic vendor tools. It does not, however, explicitly differentiate itself from the closely named sibling get_saas_negotiation_playbook or get_vendor_contract_intelligence, leaving the agent to infer the boundary.

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 preparing to renew or renegotiate a SaaS contract" gives a clear triggering situation, and the Salesforce example reinforces the pre-renewal timing context. There are no explicit exclusions or named alternatives to route away to, so it stops short of full when/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