Skip to main content
Glama

BRAINIAC Application & Pipeline Security Checks

Inspect JWTs for weak crypto and claims

appsec-config_jwt-inspect
Read-onlyIdempotent

Decode JWTs, flag alg:none, weak HMAC secrets and lifetime issues. Price $0.03 USDC. POST /api/v1/appsec-config/jwt-inspect. 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": {
      "token": "<token>"
    },
    "name": "appsec-config_jwt-inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
nowNonow, string. Optional.
tokenYestoken, string, length 10 to 16384. Required.
publicKeyPemNopublicKeyPem, string. Optional.
expectedAudienceNoexpectedAudience, string. Optional.
maxLifetimeSecondsNomaxLifetimeSeconds, integer, from -9007199254740991 to 9007199254740991. Optional.

Output Schema

NameRequiredDescriptionDefault
headerNoheader. Object.
expiredNoexpired. Boolean.
payloadNopayload. Object.
sourcesNosources. Array.
findingsNofindings. Array.
limitationsNolimitations. Array.
notYetValidNonotYetValid. Boolean.
signatureCheckedNosignatureChecked. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds genuinely new behavior: a $0.03 USDC x402 charge, the POST path, and the fact that an unpaid call returns payment terms and performs no analysis. That last point is exactly the kind of prerequisite an agent must know before calling. It does not describe output shape, but an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: purpose first, then cost and endpoint, then the payment-gating behavior. Nothing is wasted, and the most decision-relevant information is front-loaded.

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?

With an output schema present, return values need not be explained, and the description covers purpose plus the payment prerequisite that a caller must satisfy. It stops short of explaining the auxiliary parameters (publicKeyPem, expectedAudience, now), which is the only remaining gap for a five-parameter tool.

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 schema already names all five parameters, and the baseline is 3. The description's mention of lifetime issues hints at maxLifetimeSeconds/now and public-key verification hints at publicKeyPem, but it adds no explicit syntax or semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Decode JWTs') plus the exact findings it produces ('alg:none, weak HMAC secrets and lifetime issues'). No sibling in the catalog performs JWT inspection, so an agent can route to it unambiguously.

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 purpose: call it when you need to analyze a JWT. There is no explicit when-to-use vs. when-not guidance, and no hint about when to supply publicKeyPem (asymmetric algs) versus relying on HMAC secret checks, even though that choice materially changes the analysis.

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