Skip to main content
Glama

BRAINIAC Network Exposure & Certificate Tooling

Decode and validate a PKCS#10 CSR

network-exposure_csr-decode-validate
Read-onlyIdempotent

Verify CSR self-signature and check key/SAN policy. Price $0.03 USDC. POST /api/v1/network-exposure/csr-decode-validate. 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": {
      "csrPem": "<csrPem>"
    },
    "name": "network-exposure_csr-decode-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
csrPemYescsrPem, string, length 20 to 65536. Required.
policyNopolicy, object. Required.

Output Schema

NameRequiredDescriptionDefault
passNopass. Boolean.
sansNosans. Array.
sourcesNosources. Array.
subjectNosubject. String.
publicKeyNopublicKey. Object.
violationsNoviolations. Array.
limitationsNolimitations. Array.
signatureValidNosignatureValid. Boolean.
signatureAlgorithmNosignatureAlgorithm. 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?

The annotations already declare readOnly, idempotent, and open-world traits, so the bar is lower. The description usefully adds the pay-per-call model ('Price $0.03 USDC'), the POST endpoint, and critically that an unpaid call returns payment terms and 'does not run' – valuable operational context an agent must know before invoking. The POST verb alongside readOnlyHint is worth noting but isn't a true contradiction since the operation only reads/validates.

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?

Purpose is front-loaded in the first sentence, followed by concise pricing, endpoint, and payment-failure notes. Slightly repetitive of the title but each sentence carries usable information without bloat.

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-value explanation isn't required, and the description covers the operation, payment behavior, and what happens on an unpaid call. For a two-parameter tool with a documented nested policy, this is nearly complete; only sibling routing is absent.

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 schema already documents csrPem and the nested policy fields. The description's 'check key/SAN policy' hints at the policy object's role but adds no syntax or threshold detail beyond the schema. Baseline 3 is appropriate.

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+resource: 'Verify CSR self-signature and check key/SAN policy', reinforced by the PKCS#10 title. An agent can identify it as a CSR validation tool, distinct from x509-decode or chain-build. It stops short of explicitly naming a sibling, so 4 rather than 5.

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 explicit when-to-use vs when-not guidance and no comparison to siblings like x509-decode or certificate-chain-build. The only context provided is a payment precondition, which is behavioral rather than routing 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