Skip to main content
Glama

dev_tools_jwt_decode

[$x402 pago por llamada] Decodifica un JWT (header + payload). NO verifica la firma — es solo inspección, no validación criptográfica.

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

Input Schema

NameRequiredDescriptionDefault
tokenYesJWT completo (header.payload.signature).
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

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 does real work: it flags the non-verification caveat and the per-call x402 payment requirement, which are not encoded anywhere in the schema. However, it says nothing about behavior on malformed tokens, error responses, or whether the HTTP 402 path is surfaced to the caller beyond a one-word note.

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?

Two sentences, zero filler, with the payment tag and the critical non-verification caveat front-loaded. Minor friction only: the bracketed Spanish payment tag precedes the actual purpose, and the description is in a different language from the surrounding tool ecosystem.

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-token decode with no output schema, the description adequately covers what comes back (header + payload) and the key safety caveat. The remaining gap, error behavior for malformed or non-JWT input, is modest for a read-only inspection utility.

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%, so both `token` and `x_payment` are already fully documented, and the description adds little syntactic detail. The '[pago por llamada]' prefix loosely reinforces that `x_payment` is a payment header, but that meaning is already explicit in the schema.

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 (decodes) and resource (JWT header + payload) and explicitly bounds the scope by declaring it does NOT verify the signature. An agent can immediately tell this is inspection, not validation, and no sibling in the list performs JWT decoding, so there is no ambiguity to resolve.

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?

The line 'NO verifica la firma — es solo inspección, no validación criptográfica' effectively tells the agent when this tool is appropriate (debugging/inspecting a token) and when its output must not be trusted for security decisions. It does not name an alternative tool for signature verification, which keeps it short of a 5.

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