Skip to main content
Glama

BRAINIAC Agent Network Float

Measure agent concentration risk

agent-networks_agent-concentration-risk

Measure how concentrated caller-supplied agent, outlet, and operator activity is. For transaction_volume, transaction_value, and revenue, compute share_bps, top-n concentration ratios, HHI = floor(sum(share_bps^2) / 10000), and dependency rankings overall, per entity kind, and for each supplied segment dimension/label. Outage scenarios remove unavailable_ids, report affected volume/value/revenue, and compare affected volume with remaining entities' replacement_capacity. No industry HHI threshold is invented or applied. Price $0.04 USDC. POST /api/v1/agent-networks/agent-concentration-risk. 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": {
      "entities": "<entities>"
    },
    "name": "agent-networks_agent-concentration-risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
outagesNo
entitiesYes
top_countsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 burden and does well: it discloses pricing ($0.04 USDC), the 402 unpaid-call behavior, the POST endpoint, that no HHI threshold is applied, and precisely how outages are handled (remove unavailable_ids, report affected volume/value/revenue, compare with replacement_capacity). It stops short of describing the response structure or entity limits (limits live in the schema).

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

Conciseness5/5

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

Dense but front-loaded: the purpose and computation lead, exotic behaviors (outage handling, no threshold) follow, with operational facts (price, endpoint, 402) at the end. Nearly every clause adds distinct information.

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?

For a 3-parameter analytical tool with no annotations and no output schema, the description explains the computation and scenario semantics thoroughly. It could go further on output shape (what the rankings/shares return as) and on top_counts behavior, but the essentials to call it correctly are present.

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 largely does: it explains what transaction_volume, transaction_value, revenue, segments (dimension/label), outages/unavailable_ids, and replacement_capacity mean in terms of computation. The gap is top_counts, whose meaning and default behavior are not explained in prose.

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 ('Measure how concentrated ... activity is') and resource (agent, outlet, operator activity), plus the exact metrics computed. An agent can distinguish it from sibling tools like outlet-performance-benchmark or terminal-profitability without opening the schema.

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 computation described (concentration/HHI analysis with outage scenarios), but there is no explicit when-to-use or when-not guidance, and no named alternative for overlapping analyses. The 'No industry HHI threshold is invented or applied' line usefully clarifies an exclusion but is not routing guidance.

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