Skip to main content
Glama

Stratalize Intelligence

Get Vendor Contract Intelligence

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

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, open-world lookup. The description adds useful behavioral context beyond the annotations: it lists the returned fields, gives an example, identifies the source as a composite, and discloses the $0.10 USDC per-call cost. It does not clarify freshness, coverage limits, or behavior for unknown vendors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the usage trigger, followed by return values, a concrete example, source, and cost. The example and cost disclosure earn their space by making the tool easier to select and use correctly.

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?

For a one-parameter intelligence lookup with no output schema, the description gives enough detail about what is returned, including the key fields and an example. It remains slightly incomplete on data limitations, unknown-vendor handling, and exact output format.

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 coverage for the single vendor_name parameter is 0%, so the description must carry the burden. It clarifies that the tool works for 'any major vendor' and gives Salesforce as an example, but it does not define accepted name formats, aliases, legal-entity matching, or what happens when the vendor is not recognized.

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 states a specific verb and resource: it returns contract intelligence for a vendor, including term length, auto-renewal notice, escalation, and risk clauses. It is clear what the tool does, but it does not explicitly distinguish itself from close siblings such as get_vendor_negotiation_intelligence, get_vendor_benchmark, or get_software_pricing_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?

It gives a clear usage context: reviewing a new vendor agreement or benchmarking contract terms before a negotiation. It does not state when not to use it or name alternative tools for adjacent needs, so the guidance is helpful but not fully routing-aware.

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