Skip to main content
Glama

Agentic Swarm Marketplace (T54 x402 MCP)

by com.agentic-swarm-marketplace.api
OverviewDiscussionsAdmin

T54 x402 request (generic)

t54_x402_request
Idempotent

Execute any T54 seller operation by operationId with an optional query map. Prefer per-operation t54_* tools when available for clearer arguments. On HTTP 402, x402_broker_client pays then retries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoQuery string parameters as a JSON object. Keys must match OpenAPI query names for this operation (see resource openapi://agentic-swarm-t54-skus).
operation_idYesExact OpenAPI operationId. Call t54_list_operations first. Known: agentCommerceData, airdropIntelligence, constitutionAuditLite, getHealth, helloPing, peerOriginVerify, researchBrief, structuredQuery

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / operation_id / description
      Previous value: -"Exact OpenAPI operationId. Call t54_list_operations first. Known: agentCommerceData, airdropIntelligence, constitutionAuditLite, getHealth, helloPing, researchBrief, structuredQuery"New value: +"Exact OpenAPI operationId. Call t54_list_operations first. Known: agentCommerceData, airdropIntelligence, constitutionAuditLite, getHealth, helloPing, peerOriginVerify, researchBrief, structuredQuery"
  2. Changed1 schema field changed
    • changedInput schema / properties / query / anyOf
      Previous value: -[
-  {
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / query / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "t54_x402_requestOutput",
-  "type": "object"
-}New value: +null
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, openWorld=true, and destructive=false. The description adds meaningful behavioral context beyond those flags, especially the HTTP 402 behavior where x402_broker_client pays and retries. No annotation contradiction is present.

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?

Three tight sentences with no filler: one states the core function, one gives routing guidance, one discloses error/retry behavior. Each sentence earns its place and the most important information is front-loaded.

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 generic execution tool with no output schema, it adequately covers tool selection, operation lookup, parameter handling, and a key error case. A minor gap is that it does not hint at what the response shape will be, though that is inherently operation-dependent and likely documented via t54_list_operations or per-operation tools.

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%, and the schema itself already explains both operation_id and query in detail, including the known operationId values and the need to call t54_list_operations first. The description adds little beyond repeating 'optional query map', so the baseline 3 applies.

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 action ('Execute any T54 seller operation by operationId') and clearly marks itself as the generic fallback relative to the per-operation t54_* siblings. The title 'generic' and the instruction to prefer per-operation tools make its role unambiguous.

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

Usage Guidelines5/5

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

Explicitly tells the agent to prefer per-operation t54_* tools when available, and to call t54_list_operations first to obtain the exact operationId. This directly resolves the main selection question: when to use this generic tool versus its siblings.

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

All Agentic Swarm Marketplace (T54 x402 MCP) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources