Skip to main content
Glama

BRAINIAC Agent Network Float

Benchmark outlet performance

agent-networks_outlet-performance-benchmark

Compare caller-supplied outlet productivity inside peer groups of category:currency. Metrics are transactions per active day, revenue per operating hour from commission, average transaction value, commission per transaction, operating cost per transaction, and cash utilization_bps when capacity is supplied. When active_days or operating_hours are present, ranking uses the normalized per-day and per-hour figures instead of raw totals. productivity_score is the sum of competition ranks across available metrics; lower is better. explanations and formulas document every metric. No industry benchmark or external market data is used. Price $0.04 USDC. POST /api/v1/agent-networks/outlet-performance-benchmark. Unpaid calls return 402 and do 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": {
      "outlets": "<outlets>"
    },
    "name": "agent-networks_outlet-performance-benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
outletsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses the paywall ($0.04 USDC), the HTTP surface (POST /api/v1/agent-networks/outlet-performance-benchmark), and the failure mode (unpaid calls return 402 and do not run). It also explains the scoring methodology and that lower productivity_score is better, but omits rate limits, tie handling, and minimum peer-group size.

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?

Dense but front-loaded: purpose first, then metrics, then ranking rule, then pricing and endpoint. Each sentence carries a distinct fact, though the metric enumeration is a long run-on clause that could be broken for scanability.

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?

No output schema exists, and the description adequately covers what comes back (the six metrics, productivity_score as a sum of competition ranks, explanations and formulas documenting each metric). Gaps remain around response envelope shape and edge cases such as single-outlet peer groups or ties.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it does: it explains which inputs drive which derived metrics (transactions per active day, revenue per operating hour from commission, cash utilization_bps needing capacity) and that active_days/operating_hours switch ranking from raw totals to normalized figures. It does not map every nested field name (e.g. cash_available vs cash_capacity) explicitly, leaving some inference.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and object ('Compare caller-supplied outlet productivity inside peer groups of category:currency') and enumerates the six metrics produced. This is clearly distinguishable from siblings such as terminal-profitability or commission-leakage, which measure different things on different units.

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?

Establishes clear preconditions: data must be caller-supplied, outlets are grouped within category:currency peers, and active_days/operating_hours must be present for normalized ranking. 'No industry benchmark or external market data is used' functions as an explicit scope exclusion, though no sibling alternative is named for cases where the caller lacks internal 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