Skip to main content
Glama

BRAINIAC Network Exposure & Certificate Tooling

Classify port/service exposure risk

network-exposure_port-service-risk-classify
Read-onlyIdempotent

Name IANA services and assign documented risk tiers. Price $0.02 USDC. POST /api/v1/network-exposure/port-service-risk-classify. An unpaid call returns the x402 payment terms and does 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": {
      "services": "<services>"
    },
    "name": "network-exposure_port-service-risk-classify"
  }
}

Input Schema

NameRequiredDescriptionDefault
servicesYesservices, array. Required.

Output Schema

NameRequiredDescriptionDefault
resultsNoresults. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds important payment behavior beyond those annotations: the price ($0.02 USDC), the POST endpoint, and that an unpaid call returns x402 payment terms without running the 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?

The description is four short sentences and front-loads the core purpose before payment details. The HTTP method and endpoint are relevant for the x402 payment flow, though they add some technical overhead.

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?

The tool has a simple single-parameter schema and an output schema, so return values need not be explained. The description covers purpose and the non-obvious payment gating, but it could do more to explain usage context relative to sibling network-exposure tools.

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 100%, so the input schema already fully documents the 'services' array and its port/protocol/bannerHint fields. The description does not add parameter-level meaning beyond what the schema provides, which is acceptable given full coverage.

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 states a specific action: 'Name IANA services and assign documented risk tiers.' This clearly identifies the tool as a risk-classification operation, but it does not explicitly differentiate itself from sibling tools such as service-banner-fingerprint or cpe-parse-match.

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?

No guidance is given about when to use this tool versus alternatives, nor are there exclusions or prerequisites beyond the payment note. The purpose implies usage, but the description does not route the agent among sibling 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