Skip to main content
Glama

UAI x402 Security Tools

jwt-decode

JWT decode and inspect — decode header and payload without signature verification, flag expired tokens, insecure algorithms, and not-before issues for agent auth debugging. (REST equivalent: POST /api/v1/jwt-decode, $0.02)

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": {
      "jwt": "<jwt>"
    },
    "name": "jwt-decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
jwtYesJWT string to decode (no verification)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With only a title annotation, the description carries the disclosure burden and does it well: it flags that signature verification is NOT performed (a critical safety limitation), names the checks it surfaces (expiry, insecure algorithms, not-before), and discloses the REST endpoint and $0.02 cost. It doesn't state whether the call is a pure local decode or a network round-trip, which is the one remaining ambiguity.

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?

A single dense sentence front-loads the action and the verification caveat, followed by a parenthetical for REST/cost metadata. No filler.

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 tool with no output schema, the description gives enough: it names the findings returned (expired, insecure alg, not-before) and the no-verify constraint. Only missing piece is whether decoding is local or a server-side call.

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?

One parameter with 100% schema coverage, so the schema already documents 'jwt'. The description reinforces the no-verification caveat on the input but adds no format or syntax detail beyond the schema's baseline.

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 ('JWT decode and inspect') and clarifies the scope: decode header and payload WITHOUT signature verification. That distinguishes it from a verification tool, but the sibling 'jwt-inspect' sounds functionally near-identical and the description offers no basis for choosing between them.

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?

Provides an implied use case ('for agent auth debugging') and an important exclusion (no signature verification), but gives no explicit when-to-use-vs-alternative guidance, which matters given the near-duplicate 'jwt-inspect' sibling.

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