Skip to main content
Glama

get_vendor_contract_intelligence

Read-only

Use when reviewing a new vendor agreement or benchmarking contract terms before a negotiation. Returns typical contract length, auto-renewal notice window, price escalation percentage, and key risk clauses for any major vendor. Example: Salesforce standard — 36-month term, 60-day auto-renewal notice, 7% annual escalation — missing the 60-day window costs 12 months of negotiation leverage. Source: Stratalize contract 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_contract_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendor_nameYes

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. Beyond that, the description adds genuinely useful context: the data provenance ('Stratalize contract intelligence composite') and an explicit per-call cost of $0.10 USDC, which is a real constraint on invocation. It does not describe coverage limits or what happens when a vendor is absent from the composite.

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 description is front-loaded with the usage condition, then the returned fields, then a concrete example, then source and price. Every sentence carries information, and the Salesforce example makes the output shape tangible. The example sentence is somewhat long, but it is the most load-bearing part of the description.

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 explaining returns, and it does so by enumerating the four field classes and illustrating them with real values. The single-parameter schema is simple enough that little more is needed. The remaining gap is what the tool does for vendors outside the composite and whether values are vendor-specific or category averages.

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?

There is a single required parameter, vendor_name, and the schema gives it no description (0% coverage). The description only indirectly conveys meaning through 'for any major vendor' and the example 'Salesforce standard', which hints that the parameter takes a plain vendor name rather than an ID or domain. It adds modest signal but gives no format rules, casing, or behavior for unknown vendors.

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 verb and resource plus the exact fields returned: 'Returns typical contract length, auto-renewal notice window, price escalation percentage, and key risk clauses for any major vendor.' That is far more specific than the name alone. It does not, however, distinguish itself from close siblings such as get_vendor_benchmark, get_vendor_negotiation_intelligence, or get_gpo_contract_benchmark, which an agent would have to disambiguate on its own.

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 reviewing a new vendor agreement or benchmarking contract terms before a negotiation' gives a clear triggering context with a timing cue (before a negotiation). It stops short of exclusions or naming an alternative tool for adjacent needs, so the agent still has to infer which sibling to pick.

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