Skip to main content
Glama

BRAINIAC Agent Network Float

Detect dormant outlets

agent-networks_dormant-outlet-detect

Classify caller-supplied outlets as active, declining, temporarily inactive, permanently inactive, seasonal, suspended, closed, never active, or not yet active. Open days follow the supplied weekday schedule (or every day when omitted) excluding dates covered by closure, suspension, or seasonal status records. Inactivity uses open days after the last transaction through as_of_date against inactive_days_threshold and permanent_days_threshold. Decline compares recent_days volume with the preceding baseline window. Every outlet row includes evidence strings. No external dormancy threshold is invented. Price $0.04 USDC. POST /api/v1/agent-networks/dormant-outlet-detect. 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": {
      "as_of_date": "<as_of_date>",
      "outlets": "<outlets>",
      "transactions": "<transactions>"
    },
    "name": "agent-networks_dormant-outlet-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
outletsYes
schedulesNo
as_of_dateYes
recent_daysNo
transactionsYes
baseline_daysNo
status_recordsNo
decline_bps_thresholdNo
inactive_days_thresholdNo
permanent_days_thresholdNo

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 open-day derivation (supplied weekday schedule, or every day when omitted, minus closure/suspension/seasonal windows), how inactivity and decline are computed, that every row carries evidence strings, that no external threshold is invented, the $0.04 USDC price, POST endpoint, and that unpaid calls return 402 without running. It stops short of stating default values for recent_days, baseline_days, and the three thresholds when omitted.

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?

Front-loads the classification outcome, then the computation rules, then the commercial/transport facts (price, endpoint, 402). Dense but every sentence adds a constraint the agent would otherwise have to guess.

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 10-parameter classification tool with no output schema, the description gives the output labels and notes evidence strings per row, which is enough to anticipate results. The main gap is the absence of default values and the exact mapping from threshold breaches to specific labels.

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 description coverage is 0% across 10 parameters, so the description must compensate, and it largely does: it explains schedules/weekday semantics and the omitted-value rule, status_records kinds, as_of_date, recent_days vs baseline window, and both inactivity thresholds. It leaves activation_date, expected_transactions_per_active_day, and the transactions 'count' field unexplained.

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 ('Classify') and resource ('caller-supplied outlets') and enumerates the nine output labels it assigns. No sibling tool covers dormancy, so the agent can place it immediately 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 only implied: the reader infers the tool is for evaluating outlet inactivity/decline from a transaction history as of a date. There is no explicit when-to-use vs when-not-to-use statement or named alternative among the many sibling analytics tools.

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