Skip to main content
Glama

decode_jwt

Paid $0.02 (x402, USDC Base): JWT decoder - header + payload + expiry status, NO signature verification (inspection only). Args: token (string).

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

Input Schema

NameRequiredDescriptionDefault
tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full load and does disclose two valuable non-schema facts: the $0.02 x402/USDC payment on Base and that signatures are not verified. It omits error behavior for malformed tokens and whether expiry status is computed against the current time, so it adds real value but not rich behavioral context.

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?

A single compact sentence with the price, capability, and limitation front-loaded, then args last. The telegraphic parentheticals read a bit like a spec sheet but nothing is redundant.

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-argument tool with no output schema, the description covers inputs, returned fields, the pay-per-call cost, and the critical verification caveat. Only failure-mode behavior is unspecified, which is minor at this complexity.

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?

Only one parameter exists and schema description coverage is 0%, so the description's 'Args: token (string)' is the sole documentation, but it adds no format, encoding, or handling guidance beyond the obvious. Minimal compensation for the coverage gap.

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 concrete verb and resource ('JWT decoder') plus the exact output shape ('header + payload + expiry status') and the key scope limit ('NO signature verification'). No sibling tool does JWT work, so it is unambiguous against the listed toolset.

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 makes the inspection-only use case explicit and warns that signature verification is not performed, which tells the agent when not to rely on it for authentication. It stops short of naming an alternative tool or stating the conditions that would select a different approach.

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