Skip to main content
Glama

Decode JWT (no verification)

bursia_jwt_decode
Read-onlyIdempotent

Decode a JWT header and payload WITHOUT verifying its signature. Do not paste live secrets. Pure computation, free.

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

Input Schema

NameRequiredDescriptionDefault
tokenYesA JWT (three dot-separated base64url parts). Use test tokens, not live secrets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / token / description
      Added value: +"A JWT (three dot-separated base64url parts). Use test tokens, not live secrets."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is largely pre-covered. The description adds real value beyond that: it emphasizes that the signature is NOT verified (a correctness-critical trait), warns against live secrets, and notes it's pure local computation that is free. It doesn't cover malformed-token behavior, which keeps it off 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?

Front-loaded with the core action and its crucial caveat in the first sentence, then two short follow-ups for safety and computation model. Every sentence is short and purposeful, though 'free' is mild marketing that doesn't strictly aid invocation.

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 single-parameter pure-computation tool with no output schema and full annotation coverage, the description is nearly complete – purpose, safety, and non-verification behavior are all stated. It implies (but doesn't explicitly state) that the return is the decoded header and payload, which would be minor added clarity.

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?

There is a single parameter with 100% schema description coverage – the schema already explains the three dot-separated base64url format and repeats the 'test tokens' warning. The description adds no format or syntax detail beyond that, so the baseline of 3 for full-coverage schemas applies.

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 names a specific verb and resource ('Decode a JWT header and payload') and states a key scope constraint ('WITHOUT verifying its signature'). No sibling tool performs JWT decoding, so there's no ambiguity to resolve, and the no-verification scope distinguishes it from any token-validation behavior an agent might assume.

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 gives clear usage context – 'Do not paste live secrets' and implicitly 'use test tokens' – plus the fact that only decoding (not validation) is performed. It doesn't name alternatives, but no sibling offers JWT decoding, so the inference is direct. The safety caveat is actionable guidance rather than an exclusion rule.

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