Skip to main content
Glama

BRAINIAC Network Exposure & Certificate Tooling

Parse CPE strings and match criteria

network-exposure_cpe-parse-match
Read-onlyIdempotent

Unbind CPE 2.2/2.3 names and test version-range criteria. Price $0.02 USDC. POST /api/v1/network-exposure/cpe-parse-match. 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": {
      "cpe": "<cpe>"
    },
    "name": "network-exposure_cpe-parse-match"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpeYescpe, string, length 1 to 1024. Required.
criteriaNocriteria, array. Required.

Output Schema

NameRequiredDescriptionDefault
uriNouri. String.
wfnNowfn. Object.
matchesNomatches. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
formattedStringNoformattedString. String.

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?

Adds real context beyond the readOnly/idempotent/openWorld annotations: the $0.02 USDC price, the POST endpoint, and the important fact that an unpaid call returns x402 payment terms and does not execute. That last point is genuinely useful. It stops short of describing how matching is decided or what a non-match looks like, but with annotations covering the safety profile this is adequate.

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, front-loaded with the operation and then the operational constraints; nothing is padded. The endpoint path is arguably redundant with the tool name but is compact and cheap.

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?

Return values are covered by the output schema, so omitting them is fine. What is missing is semantic depth on the core value proposition: what "unbind" produces and how start/end version bounds are evaluated (including interaction between criteria string and the bound fields). Adequate but with clear gaps for a tool whose whole purpose is that evaluation.

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 coverage is 100%, so the baseline is 3. However, the schema's own descriptions are near-tautological ("criteria, string, length 1 to 1024") and never explain that the criteria array holds version-range bounds or how the four version* fields interact. The description could have compensated but only gestures at it with "test version-range criteria".

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 pair ("Unbind ... and test") against a specific resource (CPE 2.2/2.3 names, version-range criteria), which no sibling covers. The jargon "unbind" is not explained, but the CPE framing makes the operation identifiable.

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 description gives no guidance on when to use this versus the sibling tools (e.g. cvss-calculate or port-service-risk-classify) and no prerequisites or exclusions. The only conditional stated is about payment state, which is operational rather than selection guidance.

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