Skip to main content
Glama

AEGIS (McX Ventures)

AEGIS Network Forensics (custom targets)

forensics_custom
Read-only

Six-check network forensics scan against buyer-supplied targets (1-8 public hosts/IPs) Price: $0.05 USDC on Base per call, paid with x402.

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": {
      "targets": "<targets>"
    },
    "name": "forensics_custom"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetsYes1-8 public hostnames or IP addresses

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuinely useful behavior beyond them: a fixed price of $0.05 USDC on Base via x402 and that the scan is six checks. However it never enumerates the six checks, so the agent cannot predict coverage versus the narrower sibling checkers.

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?

A single tight sentence with the scan scope front-loaded and the payment cost as a trailing clause. Nothing is wasted, though the compressed 'Six-check' label dangles without explanation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 tool is a single-parameter scan, so the description should carry the return-shape burden. It covers cost and breadth but leaves the agent guessing what the six checks produce and how payment is settled, which matters for a paid, open-world call.

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?

With one parameter at 100% schema description coverage, the schema already fully documents the targets array including min/max items. The description restates the 1-8 constraint but adds no meaning beyond it, so the baseline applies.

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?

States a specific verb and resource: a network forensics scan run against caller-supplied targets. The 'custom targets' qualifier in the title hints at the distinction from forensics_run, but the description itself never names a sibling or explicitly contrasts scope, so an agent must infer the split.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage signal is the phrase 'buyer-supplied targets', which implies this is the path when you already know which hosts to scan. There is no statement of when to prefer forensics_run, ct_check, dns_check or tls_check, and no prerequisites such as whether targets must be publicly reachable or authorized.

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