Skip to main content
Glama

Stratalize Intelligence

Get Vendor Negotiation Intelligence

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

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the upstream source ('Stratalize procurement intelligence composite') and a per-call price of $0.10 USDC, which matters for an agent budgeting calls. It does not disclose coverage limits or behavior for unknown/unsupported vendors, which 'for any vendor' leaves ambiguous.

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 contents, then a concrete example, then source and price. Nothing is redundant, though the example sentence is dense and does double duty as both illustration and evidence, which slightly buries the sourcing and cost lines.

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 takes on the job of describing return contents and does so by naming five distinct output fields, plus source attribution, cost, and a worked example of the shape of the answer. For a single-parameter read-only lookup, an agent has enough to decide to call it and to interpret the result.

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% for the single vendor_name parameter, so the description must carry the meaning. The Salesforce example implies vendor_name is a plain company name rather than a ticker, domain, or legal entity, but this is inference rather than an explicit statement of expected format or matching behavior.

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?

States a specific retrieval verb and enumerates the returned artifacts (discount percentage, negotiation windows, leverage points, auto-renewal risk flags, negotiation script), which is far more informative than the title. It anchors the domain to SaaS contract renewal, though it never names which sibling it is distinct from (e.g., get_saas_negotiation_playbook or get_vendor_contract_intelligence).

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?

Opens with an explicit trigger condition: 'Use when preparing to renew or renegotiate a SaaS contract,' and the example adds the timing nuance (initiate ~90 days before renewal). It provides no when-not-use guidance and no routing to alternative sibling tools for adjacent questions such as contract terms or market rates.

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