Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

encoding_decoding_jwt

Read-onlyIdempotent

Offline JWT decoder and claim inspector: splits token, decodes header and payload, annotates claims with timestamps and expiration check.

Instructions

JWT Decoder and Claim Inspector. Decode and inspect a JSON Web Token offline: split it into header, payload, and signature, Base64URL-decode the header and payload JSON, and annotate every payload claim (with human-readable timestamps and an EXPIRED flag for past exp). This tool only decodes and does not fetch JWKS or verify the signature cryptographically; use security_jwt_generator_validator when you need to verify an HMAC or asymmetric signature, check exp/nbf against a secret or key, or assemble and sign a new token. Runs locally on the token you provide: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/minute for anonymous callers). Returns the decoded header and payload, the three raw token parts, a structure-status object, and a per-claim analysis map.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesThe JSON Web Token to decode, as a compact dot-separated string of three Base64URL parts (header then payload then signature). Must not be blank. Whitespace is trimmed before parsing.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when the token had a valid three-part structure and both header and payload decoded; otherwise the endpoint returns HTTP 400.
inputNoThe submitted token string, echoed back.
decodedJWTNoThe decoded token sections. header and payload are null when decoding failed.
tokenPartsNoThe token split on dots, before decoding. Normally three elements (header, payload, signature).
tokenStatusNoStructural assessment of the token.
claimsAnalysisNoPer-claim breakdown keyed by claim name; each entry describes one payload claim. Empty when decoding failed.
errorNoA high-level parse error message when decoding failed, or null on success.
Behavior5/5

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

Annotations already provide readOnlyHint, destructiveHint, and idempotentHint as true. The description adds valuable context: it runs locally, is read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/minute). This complements the annotations without contradiction.

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?

The description is a single, well-structured paragraph that front-loads the main purpose. Every sentence adds value: purpose, limitations, operational traits, and output. No fluff or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of JWT decoding with claim analysis, the description is comprehensive. It covers what it does, what it doesn't do (no verification), when to use, and operational details (local, rate-limited). Output schema exists, so return values are documented; the description adds the claim analysis aspect.

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

Parameters4/5

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

With 100% schema description coverage, the baseline is 3. However, the description adds meaning beyond the schema by explaining the decoding process, splitting into parts, and the output structure (header, payload, raw parts, claim analysis). This adds value, but the schema already describes the token parameter well.

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 clearly states the tool decodes and inspects a JSON Web Token offline, splitting it into header, payload, and signature. It specifies the verb 'decode and inspect' and the resource 'JSON Web Token', and distinguishes itself from the sibling 'security_jwt_generator_validator' by clarifying it does not verify signatures.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool versus the alternative 'security_jwt_generator_validator', which is for verification and assembly. It clearly indicates that this tool only decodes and does not fetch JWKS or verify signatures, guiding the agent to the correct tool for specific tasks.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server