Skip to main content
Glama

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

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, open-world), and the description adds genuinely new operational context: the upstream source ('Stratalize PE Intelligence composite') and a per-call price of $0.02 USDC, which matters for cost-aware agents. It does not disclose whether figures are survey-derived versus modeled, or any freshness/coverage caveats, which would have earned a 5.

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 output contents, then a concrete worked example, then source and price in short trailing clauses. The dollar-figure example is longer than strictly necessary but it does make the output shape concrete, so it mostly earns its space.

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 low-complexity, two-optional-parameter read tool with no output schema, the description adequately conveys what comes back and at what cost. It is incomplete on the one thing an agent must decide before calling: what values 'sector' accepts and what the defaults produce when both optional parameters are omitted.

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 coverage is 0% for two parameters, so the description carries the full burden and largely fails. 'company_count' is only hinted at via the example ('across 10-company portfolio'), and 'sector' is never explained at all — no accepted values, no default behavior when the zero-required-param call is made with neither field supplied.

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 ('benchmarking portco technology spend') and explicitly lists what is returned: median software spend per company, category breakdown, and savings opportunity percentage. It is clearly distinguishable from neighbors like get_pe_return_benchmark, though it never names an alternative tool directly.

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?

Opens with an explicit trigger ('Use when benchmarking portco technology spend for PE operating partners or building a software cost reduction case'), which tells the agent the exact analysis context. It gives no when-not-to-use guidance and does not point to a sibling for adjacent questions such as return or vendor data.

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