Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_jwt_decode

Read-onlyIdempotent

Decode a JWT token's header and payload fields to inspect claims and metadata, without asserting signature verification.

Instructions

Decode JWT header and payload fields without claiming signature verification.

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": "oc_jwt_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 the safety profile is covered. The description adds genuine value beyond them by disclaiming signature verification, which prevents an agent from treating decoded output as authenticated data. It does not describe malformed-token or partial-decode behavior, keeping it below a 5.

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?

A single front-loaded sentence with no filler; the caveat is attached directly to the action statement. It is efficient, though the terseness leaves the parameter format unstated.

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?

With one required parameter, annotations covering safety, and an output schema that documents the return shape, the description has little heavy lifting left. The remaining gap is input format guidance for the token string, which matters for an agent assembling the call.

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?

There is one parameter at 0% schema description coverage, so the schema says nothing about the 'token' field. The description implies the value is a JWT but does not clarify whether it accepts a raw compact-serialized string, whether a 'Bearer ' prefix is tolerated, or what happens with malformed input, so it fails to compensate for the coverage gap.

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?

Specific verb 'decode' targeting a specific resource 'JWT header and payload fields', which is more precise than a generic 'decode JWT'. It does not name the sibling oc_jwt_audit or explain how decoding differs from auditing, so sibling differentiation is left to inference.

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?

The clause 'without claiming signature verification' implies the appropriate scope (inspecting claims, not validating trust) but never states when to pick this over oc_jwt_audit. No explicit when/when-not framing or prerequisites are given.

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