Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

JWT decode: decode a JWT token's header and payload and check its expiry

jwt_decode
Read-only

JWT decode without a key: the header and payload of a JSON Web Token (the signature is not verified), with issued-at, not-before and expiry as dates and whether it has expired. The token is not stored. Do not use the result to trust a token. Use to debug auth flows. Example: token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjMiLCJleHAiOjE3OTIyODE2MDB9.sig. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not 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": "jwt_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe JWT

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that the signature is unverified, that the token is not stored, that output includes iat/nbf/exp rendered as dates plus an expired flag, and the pricing model including free failures. It also implicitly reconciles the non-obvious idempotentHint=false by noting each call is charged, so repeats are not free.

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 semantics and the safety caveat before pricing details, and every sentence carries information. Slight redundancy between 'The token is not stored' and 'Reads or computes only and changes nothing', plus the title-style opening restating the name.

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?

There is no output schema, yet the description still describes the return shape (header, payload, dates, expiry flag) and the critical caveat that the signature is not verified. For a one-parameter tool this leaves nothing an agent needs missing.

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?

Schema coverage is 100% and the single parameter is required, so the schema does most of the work. The description adds a concrete worked example token showing the three dot-separated segments, which gives the agent a usable format cue beyond 'The JWT'.

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?

States a specific verb and resource (decode a JWT's header and payload) and immediately delimits scope: signature is not verified, expiry is checked. An agent can tell this apart from sibling tools like hash or hmac, which produce signatures rather than inspect them.

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?

Gives an explicit when-not ('Do not use the result to trust a token') and a when ('Use to debug auth flows'), which is more than most definitions offer. It stops short of naming a specific alternative tool for verified decoding, so it falls one step below fully explicit routing.

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.