Skip to main content
Glama

BRAINIAC Agent Network Float

Score terminal profitability

agent-networks_terminal-profitability

Score caller-supplied payment terminals from transaction counts, values, fee rules, revenue shares, and operating costs. Fees may be fixed, a rate in basis points, or tiers by cumulative count. revenue_share_bps is the share of the fee the terminal keeps; omitted means 10000. Each terminal keeps its own currency code. No amount is converted. profit_margin_bps is net profit over revenue in basis points. break_even_count is the transaction count that covers the period costs at the average revenue per transaction from the supplied mix. Ranking is by net profit inside each currency. No ledger is fetched or stored. Price $0.04 USDC. POST /api/v1/agent-networks/terminal-profitability. 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>",
      "transaction_types": "<transaction_types>",
      "transactions": "<transactions>"
    },
    "name": "agent-networks_terminal-profitability"
  }
}

Input Schema

NameRequiredDescriptionDefault
terminalsYes
transactionsYes
transaction_typesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

With no annotations at all, the description carries the full burden and does so: it discloses the paid endpoint and price, that unpaid calls return 402 and do not execute, that no ledger is fetched or stored (no side effects), that no currency conversion occurs and ranking is per-currency, and the default of 10000 for an omitted revenue_share_bps.

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?

It is dense and front-loaded with the computational model, then the metric definitions, then the commercial/protocol facts. Nearly every clause carries information, though the list-style phrasing of the first sentence and the scattered ordering of the currency rule are slightly less tidy than ideal.

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?

There is no output schema, so the description must define the returns, and it does: profit_margin_bps as net profit over revenue in basis points, break_even_count derived from period costs over average revenue per transaction, and ranking by net profit within each currency. It stops short of describing the full per-terminal result shape, which is the only meaningful gap for a scored-analytics tool.

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%, yet the description explains the fee model that dominates the schema: fixed amount, rate in basis points, or tiers by cumulative count, plus revenue_share_bps as the terminal's kept share of the fee. It leaves notable gaps — the units of 'value' and 'amount', the meaning of the costs fields, and tier ordering/up_to semantics — so it does not fully close the coverage gap.

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 and resource ('Score caller-supplied payment terminals') and enumerates the exact inputs consumed (transaction counts, values, fee rules, revenue shares, operating costs). It is unmistakable what the tool computes, though it never explicitly contrasts itself with the many other agent-networks analytics tools.

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?

'Caller-supplied' and 'No ledger is fetched or stored' imply the tool is for scoring data the agent already holds rather than querying a backend. There is no explicit when-to-use or when-not-to-use guidance and no naming of an alternative, so the selection signal is only implicit.

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