Skip to main content
Glama

BRAINIAC Agent Network Float

Measure terminal downtime impact

agent-networks_terminal-downtime-impact

Quantify agent terminal outages using supplied availability intervals, historical day totals, and optional per-hour averages. measured_* values come only from history rows on the outage start date. estimated_lost_* values come only from supplied averages. Restoration priority ranks terminals by estimated lost commission, then value, then transactions, then downtime. No market demand model is invented. Price $0.04 USDC. POST /api/v1/agent-networks/terminal-downtime-impact. 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": {
      "terminals": "<terminals>",
      "outages": "<outages>"
    },
    "name": "agent-networks_terminal-downtime-impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
historyNo
outagesYes
averagesNo
terminalsYes

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?

With no annotations, the description carries the full burden and does so well: it states pricing ($0.04 USDC), the POST endpoint, and that unpaid calls return 402 and do not run. It also discloses computation semantics — measured_* from history rows on the outage start date, estimated_lost_* from supplied averages, and a defined ranking tiebreaker order. It omits any description of the response shape, but the behavioral disclosure is otherwise rich.

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?

The description is front-loaded with the purpose, then semantics, then cost and transport details. Six short sentences, each carrying information; no filler. The pricing/endpoint/payment lines could be tightened into one clause, but nothing is wasted.

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 complex analytical tool with zero schema coverage and no output schema, the description covers input provenance, computation rules, ranking behavior, scope limits, cost, and payment failure mode. The remaining gaps — return structure and per-field semantics for terminals and object members — keep it from being fully complete.

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 0%, so the description must compensate. It adds real meaning by mapping outages to "availability intervals," history to "historical day totals," and averages to "optional per-hour averages," and explains how those values feed measured vs estimated outputs. The required `terminals` parameter and the fields inside each object (commission, commission_bps, transaction_value, etc.) receive no explanation, leaving notable gaps.

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 opens with a specific verb+resource: "Quantify agent terminal outages" using availability intervals, historical day totals, and optional per-hour averages. That clearly distinguishes it from siblings like terminal-profitability or commission-leakage. It stops short of explicitly naming an alternative, so it is clear but not sibling-routed.

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?

The scenario is implied by the input requirements (outages plus history rows), which tells an agent when the tool applies. The line "No market demand model is invented" acts as a useful scope boundary. However, there is no explicit when-to-use vs when-not or pointer to any alternative, leaving the agent to infer.

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