Skip to main content
Glama

Stratalize Intelligence

Get Portfolio Vendor Intelligence

get_portfolio_vendor_intelligence
Read-only

Use when conducting vendor diligence for a PE or VC portfolio company before a value creation initiative. Returns market rate data, brand index snapshot, and competitive displacement signals for any vendor. Example: Portco using Salesforce at $12,400/mo — market median $8,400/mo, 48% above market — immediate renegotiation opportunity with $48K annual EBITDA recovery. Source: Stratalize composite diligence. $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_portfolio_vendor_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendor_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only and non-destructive safety. The description adds genuinely non-structured behavior: a $0.10 USDC per-call cost (critical for an agent deciding whether to invoke), the data provenance ('Stratalize composite diligence'), and the specific payload contents. It does not cover latency, failure modes, or coverage limits.

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 use case, then outputs, then a worked example, then source and price. The dollar example is illustrative rather than padding, but the sentence is dense and could be split for readability.

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 correctly enumerates return contents and adds cost and source. What an agent still lacks — name normalization rules and what happens for unknown vendors — is a modest gap for a single-parameter read tool.

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?

One required parameter with 0% schema coverage, so the description must compensate. The Salesforce example implies vendor_name accepts a common product/vendor name rather than a legal entity ID, which is modest but useful signal. It never states formatting rules, aliases, or handling of ambiguous names.

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 verb (returns) plus three concrete output types — market rate data, brand index snapshot, competitive displacement signals — for 'any vendor.' The PE/VC portfolio diligence framing differentiates it from the generic market-rate siblings, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear trigger ('vendor diligence for a PE or VC portfolio company before a value creation initiative'), which is real when-to-use guidance. But it offers no exclusions and no routing among the many overlapping siblings (get_vendor_market_rate, get_vendor_benchmark, get_saas_market_intelligence), leaving the agent to guess which to call.

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