Skip to main content
Glama

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. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already establish readOnly/openWorld/no-destructive, so the description's added value is the cost disclosure ($0.10 USDC per call) and the data provenance ('Stratalize composite diligence'), both of which are genuinely decision-relevant to an agent. It also enumerates the three output categories, useful given no output schema exists. It omits what happens for an unrecognized vendor or how stale the composite data is.

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

Conciseness3/5

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

The trigger is correctly front-loaded in the first sentence, and the returned-data list is efficient. The pricing example, however, is long and promotional ('$12,400/mo — market median $8,400/mo, 48% above market — immediate renegotiation opportunity with $48K annual EBITDA recovery'), spending a large share of the description on sales framing rather than operational guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no output schema, the description does cover the return categories, source, and price, which is reasonably complete. The gaps are the unelaborated input format and no differentiation from the many sibling vendor-intelligence tools, which is the main risk to correct invocation.

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

Parameters2/5

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

The single parameter vendor_name has 0% schema description coverage, so the description must carry the burden and largely fails. The worked example implies a product/vendor name like 'Salesforce', but nothing states the expected format, whether legal entity vs. product name matters, or how fuzzy matching is handled.

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 and resource: returns market rate data, brand index snapshot, and competitive displacement signals for a named vendor, framed for PE/VC portfolio diligence. The scope is clear, but it never distinguishes itself from heavily overlapping siblings such as get_vendor_market_rate and get_vendor_benchmark, which appear to return much of the same rate data.

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 usable trigger ('conducting vendor diligence for a PE or VC portfolio company before a value creation initiative'), which is more than most tools offer. However, there are no exclusions, no prerequisites, and no routing to or away from the near-duplicate vendor-rate siblings, so an agent facing get_vendor_market_rate vs. this tool has no basis to choose.

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