Skip to main content
Glama
swarm-agent-operator

swarm-x402-mcp

by swarm-agent-operator
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

SWARM utilities

utilities

Generate UUIDs, hashes, base64, URL encodings, secure passwords, and convert timestamps through a paid per-call service.

Instructions

UUIDs, hashes, base64, URL encoding, secure passwords and timestamp conversion. Price: $0.02 per call. Calls SWARM's shop over the network and, with SWARM_WALLET_KEY set, pays in USDC on Base via x402 (the live quote is checked against SWARM_MAX_USD before paying; charged only on success).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNoHow many to generate
tNoTimestamp to convert
opYesOperation, e.g. uuid, hash, base64, password, timestamp (see https://swarm-agent.net/openapi.json)
algoNoHash algorithm
textNoInput text, for operations that take one
lengthNoPassword length

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / algo / description
      Previous value: -"Hash algorithm (op=hash). Default sha256."New value: +"Hash algorithm"
    • changedInput schema / properties / length / description
      Previous value: -"Password length (op=password). Default 16."New value: +"Password length"
    • changedInput schema / properties / length / maximum
      Previous value: -128New value: +9007199254740991
    • changedInput schema / properties / length / minimum
      Previous value: -4New value: +-9007199254740991
    • changedInput schema / properties / n / description
      Previous value: -"How many UUIDs (op=uuid). Default 1."New value: +"How many to generate"
    • changedInput schema / properties / n / maximum
      Previous value: -100New value: +9007199254740991
    • changedInput schema / properties / n / minimum
      Previous value: -1New value: +-9007199254740991
    • changedInput schema / properties / op / description
      Previous value: -"Which utility to run. Anything other than the listed ones is treated as `timestamp`."New value: +"Operation, e.g. uuid, hash, base64, password, timestamp (see https://swarm-agent.net/openapi.json)"
    • removedInput schema / properties / op / enum
      Removed value: -[
-  "uuid",
-  "hash",
-  "base64-encode",
-  "base64-decode",
-  "url-encode",
-  "url-decode",
-  "password",
-  "timestamp"
-]
    • changedInput schema / properties / t / description
      Previous value: -"The timestamp to convert (op=timestamp)."New value: +"Timestamp to convert"
    • changedInput schema / properties / t / type
      Previous value: -"string"New value: +[
+  "string",
+  "number"
+]
    • changedInput schema / properties / text / description
      Previous value: -"The input for hash, base64-* and url-*."New value: +"Input text, for operations that take one"
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing a concrete cost ($0.02/call), the network flow (calls SWARM's shop), the payment rail (USDC on Base via x402 gated on SWARM_WALLET_KEY), the spend guardrail (quote checked against SWARM_MAX_USD) and that charging occurs only on success. The annotations only flag openWorld/non-idempotent; the description supplies the financially material behavior an agent must know before invoking.

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, front-loaded with the operation list and followed by the pricing/payment constraint; no filler. Slightly dense on payment mechanics but every clause carries decision-relevant information.

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 multi-op dispatcher with no output schema, the description covers the operation families and the non-obvious payment/guardrail behavior, and delegates op details to the referenced openapi.json. What is missing is which parameters apply to which op, but that is explicitly pointed to externally.

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 all six parameters and the baseline is 3. The description adds no per-parameter meaning beyond naming the operation families, leaving op-to-parameter mapping to the external openapi.json link.

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 first sentence enumerates the concrete operations (UUID, hash, base64, URL encoding, passwords, timestamps), so the agent knows what the tool produces despite the generic name 'utilities'. It does not differentiate itself from the unrelated siblings (code_health, summary, report), but those are clearly distinct domains.

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 guidance on when to use this tool versus the alternatives, nor prerequisites beyond the payment note. It tells the agent how billing works but not when the dispatcher is the right call.

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