Skip to main content
Glama

AEGIS (McX Ventures)

AEGIS Network Forensics (fixed basket)

forensics_run
Read-only

Six-check network forensics scan — TLS, CT, DNS, NTP, portal, route Price: $0.01 USDC on Base per call, paid with x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "forensics_run"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 already declare readOnlyHint=true and openWorldHint=true, and the description adds genuinely useful context beyond them: the fixed six-check basket contents and a concrete cost of $0.01 USDC on Base paid via x402. However, it says nothing about what the scan returns, how long it takes, or whether failures of individual checks are reported — notable for an external-network operation.

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 sentence with no filler, front-loading the six checks before the pricing clause. The price/payment detail is appended awkwardly mid-sentence rather than as a clean second clause, but no content is wasted.

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?

With no input schema and no output schema, the description carries the burden for both input and output expectations. It fully covers the input side (no arguments) and payment, but leaves the return shape — one aggregated verdict vs. six per-check results — entirely unspecified.

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?

The tool takes zero parameters, so the baseline applies and there is nothing for the description to disambiguate. The enumeration of the six checks reasonably maps to the implicit scope of the zero-argument call, but no parameter-level meaning is needed or added.

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 ('network forensics scan') and enumerates the exact six checks performed — TLS, CT, DNS, NTP, portal, route — so the agent knows the scope precisely. The 'fixed basket' framing in the title implies an alternative, but the description body never names forensics_custom, so sibling differentiation is only implicit.

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?

There is no explicit when-to-use guidance and no exclusion or alternative named. The word 'fixed' hints that a customizable counterpart exists, but the agent must infer that forensics_custom is the alternative for a chosen subset rather than being told so.

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