Skip to main content
Glama

textokit_dev_utils

Hash, HMAC, JWT decode, UUID, base64 and time zone utilities. 0.001 USDC per call (x402, Base), first 10 calls/day per IP free; an unpaid call returns the x402 payment requirements. Free sample: textokit_sample.

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": {
      "op": "<op>"
    },
    "name": "textokit_dev_utils"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYesOperation to run.
toNoIANA target time zone for tz_convert (default UTC).
fromNoIANA source time zone for tz_convert (default UTC).
valueNoInput text, token, URL, timestamp or local datetime (depends…
secretNoSecret for hmac or for optional HS256 verification in…
algorithmNoHash algorithm for hash and hmac (default sha256).
payment_signatureNoOptional, legacy: base64 x402 v2 payment payload. Preferred: params._meta["x402/payment"]. Never a private key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional base64 x402 v2 payment payload for the requirements of a prior unpaid call. Never a private key."New value: +"Optional, legacy: base64 x402 v2 payment payload. Preferred: params._meta[\"x402/payment\"]. Never a private key."
  2. Changed3 schema fields changed
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional. Base64 x402 v2 payment payload signed by YOUR wallet for the requirements returned by a previous unpaid call. Never a private key."New value: +"Optional base64 x402 v2 payment payload for the requirements of a prior unpaid call. Never a private key."
    • changedInput schema / properties / secret / description
      Previous value: -"Secret for hmac or for optional HS256 verification in jwt_decode."New value: +"Secret for hmac or for optional HS256 verification in…"
    • changedInput schema / properties / value / description
      Previous value: -"Input text, token, URL, timestamp or local datetime (depends on op)."New value: +"Input text, token, URL, timestamp or local datetime (depends…"
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well by disclosing the payment model: 0.001 USDC per call via x402 on Base, first 10 calls/day per IP free, and unpaid calls return x402 payment requirements. It does not describe response formats or error behavior for individual operations, but the payment and access behavior is the critical missing piece that annotations would normally cover.

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?

Two tight sentences, front-loaded with the capability list and followed immediately by the pricing, free-tier, unpaid-call, and free-sample pointers. No sentence is wasted, and the most decision-relevant information comes first.

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

Completeness3/5

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

The description covers capabilities and payment behavior, and the schema is fully documented, but there is no output schema and the description does not explain what each operation returns. For a multi-operation utility tool, an agent still has to infer return formats such as hash encoding, JWT decode output shape, or base64 output, which leaves a meaningful gap.

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 the schema already documents every parameter, including op, value, secret, algorithm, and payment_signature. The description adds no parameter-level meaning beyond naming some of the operations, and it even omits two enum operations from its prose, so baseline 3 is appropriate.

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 concrete capabilities (hash, HMAC, JWT decode, UUID, base64, time zone utilities), which is far more specific than the tool name alone. It is slightly incomplete because the schema enum also includes url_parse and unix_to_iso, which are not named in the description, and it gives no sibling differentiation beyond pointing to the free sample.

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

Usage Guidelines3/5

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

Usage is implied by the listed operations and the pointer to textokit_sample for a free sample, but there is no explicit when-to-use guidance, no when-not-to-use guidance, and no comparison to alternatives beyond the sample tool. The pricing and free-tier details are useful context but do not substitute for selection 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.