Skip to main content
Glama

JWT Decoder API - read header, claims and expiry

jwt_decoder
Read-onlyIdempotent

Decode a JSON Web Token: header, payload claims, algorithm, expiry and issued-at as dates. Signature is not verified. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/jwt-decoder.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIxMjMiLCJleHAiOjE5MDAwMDAwMDB9.c2ln"
    },
    "name": "jwt_decoder"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses that the signature is NOT verified (a critical security caveat), that processing happens server-side with files deleted immediately and nothing stored, plus concrete rate limits (25 calls/day per IP) and per-call pricing via x402. This is exactly the behavioral context annotations cannot express.

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 tight sentences: capability and outputs first, then the verification caveat, then privacy/limits/pricing. No filler, and the most decision-relevant constraint 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?

For a one-parameter, no-output-schema tool, the description covers what is returned, the security limitation, privacy, quota and cost. Only minor gaps remain, such as what happens on an invalid or malformed token.

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%, but the schema's own description is uninformative ("The text"). The description implies the single parameter is the JWT string to decode, which adds modest meaning over the schema, but it never states format expectations or error behavior for malformed tokens.

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 and resource ("Decode a JSON Web Token") and enumerates exactly what is extracted: header, payload claims, algorithm, expiry and issued-at as dates. This makes it distinguishable from generic siblings like base64_encode_decode, though no sibling is named explicitly.

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 operation itself (you have a JWT and want to inspect it), and the "Signature is not verified" line tells the agent this is inspection only, not validation. There is no explicit when-to-use versus alternative guidance and no stated exclusions.

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