Skip to main content
Glama

UAI x402 Security Tools

jwt-inspect

JWT decode and inspect for agent auth debugging — decode header and payload, flag expired tokens, insecure algorithms, and not-before issues. Search-friendly alias for jwt-decode. (REST equivalent: POST /api/v1/jwt-inspect, $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-inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
jwtYesJWT string to decode (no verification)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no substantive annotations beyond the title, the description carries the behavioral burden and does well: it discloses that decoding is non-verifying, lists specific issues it flags, and gives the REST equivalent and cost. It does not describe error behavior for malformed tokens or output shape, so it is informative but not exhaustive.

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 front-loaded with the core decode/inspect purpose and uses compact language to cover use case, flagged issues, alias relationship, and REST/pricing context. There is little wasted wording.

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 simple one-parameter inspection tool with no output schema, the description covers the key behavior: decoding, no verification, and specific flagged conditions. It is complete enough to call correctly, though it could mention malformed-input handling or return shape.

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 description coverage is 100%, and the single jwt parameter is documented as a JWT string with no verification. The description does not add parameter-specific syntax or format guidance beyond what the schema already provides, so baseline 3 is appropriate.

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 uses a specific verb and resource: decode and inspect JWT tokens for agent auth debugging. It also identifies the tool as a search-friendly alias for jwt-decode, which clarifies its relationship to a sibling rather than leaving overlap ambiguous.

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 by naming agent auth debugging and explains that this is an alias of jwt-decode. It does not state explicit exclusions or when to prefer a different alternative, so it falls short of full when/when-not guidance.

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