Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_jwt_audit

Audit JWT structure and claims to identify alg=none, missing expiry, and issuer or audience mismatches for evidence-backed review; signature verification is not performed.

Instructions

Audit JWT structure and claims for evidence-backed review items such as alg=none, missing expiry, issuer mismatch, and audience mismatch. Signature verification is never implied.

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": {
      "engagement_id": "<engagement_id>",
      "token": "<token>"
    },
    "name": "oc_jwt_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
engagement_idYes
expected_issuerNo
expected_audienceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Beyond the annotations, the description discloses the significant behavioral limitation that its findings must not be taken as evidence of signature verification. However, it does not clarify whether engagement_id involves persistence or other side effects, leaving the non-read-only and non-idempotent annotations without useful context.

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?

Two compact sentences front-load the operation and concrete checks, then end with the critical verification caveat. There is no filler or redundant restatement of structured fields.

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?

The description covers the core purpose and a crucial interpretive limitation, while the output schema removes the need to enumerate return fields. It remains incomplete for reliable invocation because the engagement identifier and optional issuer/audience behavior are unexplained, and alternatives are not identified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description only partially compensates: JWT makes the token input broadly intelligible, and issuer/audience mismatch relates to the two expected-claim parameters. It never explains engagement_id, the expected token encoding, or whether omitted expected_issuer and expected_audience values disable their corresponding checks.

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 gives a specific verb and resource—auditing JWT structure and claims—and concretely identifies review items such as alg=none, missing expiry, and issuer or audience mismatch. The emphasis on evidence-backed findings distinguishes an audit from the sibling oc_jwt_decode's likely decoding role without relying on the sibling name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It establishes the appropriate context: use the tool for evidence-backed JWT structure and claims review. 'Signature verification is never implied' supplies an important limitation, but there is no explicit routing to oc_jwt_decode for simple decoding or to another tool when signature validation is required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools