Skip to main content
Glama

BRAINIAC Equity Analytics

Peer multiple stats and implied value

equity-analytics_peer-multiples
Read-onlyIdempotent

Summarise peer EV/EBITDA, P/E and related multiples with optional IQR trimming, and imply enterprise, equity and per-share values for a target. Price $0.03 USDC. POST /api/v1/equity-analytics/peer-multiples. An unpaid call returns the x402 payment terms and does not run.

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": {
      "target": "<target>",
      "peers": "<peers>",
      "multiples": "<multiples>"
    },
    "name": "equity-analytics_peer-multiples"
  }
}

Input Schema

NameRequiredDescriptionDefault
peersYespeers, array. Required.
targetYestarget, object. Required.
multiplesYesmultiples, array. Required.
trimOutliersIqrNotrimOutliersIqr, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
statsNostats. Object.
impliedNoimplied. Object.
sourcesNosources. Array.
limitationsNolimitations. Array.

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 declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new behavioral facts: a $0.03 USDC charge, the POST endpoint, and that an unpaid call returns x402 payment terms without executing. It stops short of describing statistical treatment (median vs mean) or error behavior.

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?

Three short, front-loaded sentences: capability first, then price, then transport and payment failure mode. The raw endpoint path is marginally redundant filler for an agent, but nothing is padded or repeated.

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 an output schema present the description need not explain return values, and annotations plus a fully covered schema carry the safety and parameter load. What remains missing is domain-level behavior an agent would want before paying: how outliers are trimmed, whether a single summary statistic or a range is produced, and validation rules for peer sets.

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 description coverage is 100%, so every parameter, including the nested peer and target objects, is already documented, which sets the baseline at 3. The description adds only that trimming is IQR-based and that multiples feed the implied-value calculation, without explaining how target fields map to which multiple or what trimming does to the peer sample.

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 names specific operations (summarise peer EV/EBITDA, P/E and related multiples; imply enterprise, equity and per-share values for a target), which is far more than a restatement of the name. It implicitly separates itself from siblings like dcf-valuation or financial-ratios by centering on peer-derived multiples, but it never explicitly contrasts with them.

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?

Usage is implied by the described workflow (peer set plus target plus chosen multiples), and the payment note clarifies what happens on an unpaid call. However, there is no guidance on when to prefer this over dcf-valuation or financial-ratios, nor any prerequisite such as minimum peer count for stable statistics.

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