Skip to main content
Glama

BRAINIAC Network Exposure & Certificate Tooling

Calculate CVSS v3.1 and v4.0 scores

network-exposure_cvss-calculate
Read-onlyIdempotent

Validate a CVSS vector and compute base/temporal/environmental or v4 scores. Price $0.02 USDC. POST /api/v1/network-exposure/cvss-calculate. 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": {
      "vector": "<vector>"
    },
    "name": "network-exposure_cvss-calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
vectorYesvector, string, length 8 to 512. Required.

Output Schema

NameRequiredDescriptionDefault
scoreNoscore. Number.
validNovalid. Boolean.
sourcesNosources. Array.
versionNoversion. String.
severityNoseverity. String.
limitationsNolimitations. Array.
macroVectorNomacroVector. String.
nomenclatureNonomenclature. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely non-redundant behavior: the $0.02 USDC price and the fact that an unpaid call returns x402 payment terms and does not execute. That payment gate is the kind of detail an agent cannot infer from structured fields.

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?

Three short sentences, with the core capability front-loaded and the payment caveat immediately after. The raw POST endpoint path is arguably noise for an MCP caller, but nothing is padded or buried.

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?

An output schema exists, so return values need not be explained, and the single parameter is fully documented in the schema. Combined with the payment behavior, the description covers what an agent needs to call it correctly. Minor gaps remain around error behavior for an invalid vector and the v3.1 versus v4 selection mechanism.

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?

There is a single parameter with 100% schema description coverage, which sets the baseline at 3. The description mentions that a vector is validated and that base/temporal/environmental or v4 scoring modes exist, which hints at vector content, but it adds no syntax, format, or version-specific detail beyond the schema. Baseline 3 is correct.

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 names a specific verb pair and resource: 'Validate a CVSS vector and compute base/temporal/environmental or v4 scores.' That is precise enough to distinguish it from every sibling, none of which deal with CVSS scoring. It stops short of naming a sibling or an explicit exclusion, so it is a strong 4 rather than a 5.

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 implied by the single-purpose statement, and the payment note functions as a prerequisite for a successful call. However, there is no explicit when-to-use guidance, no when-not-to-use condition, and no mention of any alternative or follow-up tool. Adequate but with a clear gap.

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