Skip to main content
Glama

Stratalize Intelligence

Get Pe Portfolio Benchmark

get_pe_portfolio_benchmark
Read-only

Use when benchmarking portco technology spend for PE operating partners or building a software cost reduction case across a portfolio. Returns median software spend per company, category breakdown, and savings opportunity percentage. Example: Mid-market portco median $480K/yr — 18% savings opportunity through vendor consolidation — $86K/portco recovery across 10-company portfolio = $860K EBITDA improvement. Source: Stratalize PE Intelligence composite. $0.02 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_pe_portfolio_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectorNo
company_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), and the description adds genuinely useful behavioral facts: the data source (Stratalize PE Intelligence composite) and a per-call price of $0.02 USDC. It stops short of describing latency, caching, or freshness of the composite data.

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 payload, then a quantified example, source, and price. The example's arithmetic is somewhat dense but earns its place by showing how the savings figure is consumed.

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?

With no output schema, the description usefully names the three returned fields, but for a two-parameter tool with zero schema documentation it leaves parameter meaning and valid inputs unstated. An agent can call it with no arguments but cannot confidently supply a sector.

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?

Schema description coverage is 0% and the description never explains the two parameters, 'sector' and 'company_count'. The worked example only indirectly hints that company_count scales the portfolio math ('across 10-company portfolio'), and 'sector' is entirely unaddressed, leaving the caller to guess accepted values.

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 pairs a specific verb with a specific resource: benchmarking portco technology/software spend, returning median spend per company, category breakdown, and savings percentage. That scope is narrow enough to distinguish it from return-oriented or category-spend siblings, though no sibling is named explicitly.

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?

The opening clause states a clear when-to-use: 'Use when benchmarking portco technology spend for PE operating partners or building a software cost reduction case across a portfolio.' It defines the audience and the decision context but gives no exclusions or alternative-tool routing.

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