Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

internet-jwt

Generates a random JSON Web Token for testing authentication flows, with optional custom header, payload, and reference date.

Instructions

Generates a random JWT (JSON Web Token).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "internet-jwt"
  }
}

Input Schema

NameRequiredDescriptionDefault
headerNoThe header to use for the token.
payloadNoThe payload to use for the token.
refDateNoThe date to use as reference point for the newly generated date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and it is thin. It does not say whether the token is signed, whether it is safe/test-only, what happens when header or payload are omitted, or what defaults are used — all critical for a security-adjacent generator.

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 short sentence with no wasted wording, front-loaded with the core action. It is efficient, though its brevity borders on under-specification rather than elegance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with nested object parameters, zero annotations, and no output schema, the definition says nothing about return shape, default behavior for omitted fields, or how refDate influences generation. An agent cannot predict the result of calling it without guessing.

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 each of the three parameters (header, payload, refDate) is already documented in the schema. The description adds only the word 'random', which hints at default generation when inputs are omitted but doesn't explain it. Baseline 3 applies.

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?

The description names a specific verb and resource ('Generates a random JWT (JSON Web Token)') and expands the acronym, so an agent knows exactly what is produced. It does not differentiate from the sibling 'internet-jwtAlgorithm', which an agent could plausibly confuse with this tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use, when-not-to-use, or alternative guidance. The description never tells the agent to prefer this over 'internet-jwtAlgorithm' or any other sibling, so selection must be inferred from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools