Skip to main content
Glama

Agentic Swarm Marketplace (T54 x402 MCP)

by com.agentic-swarm-marketplace.api
OverviewDiscussionsAdmin

Contract monitoring subscription (Base USDC x402)

contract_monitor_subscribe
Idempotent

Subscribe to 30-day continuous monitoring of up to 10 EVM contract addresses. Fires webhook alerts on admin key movement, liquidity drops, claim condition changes, or new critical Slither findings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressesYesUp to 10 0x-prefixed EVM addresses to watch
thresholdsNoOptional JSON object for alert sensitivity (e.g. liquidity drop %, admin key moves). Omit or {} for seller defaults.
webhook_urlYesHTTPS URL that receives POST alerts when risk thresholds breach
duration_daysNoSubscription length in days (default 30; max per seller policy).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / thresholds / anyOf
      Previous value: -[
-  {
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / thresholds / 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": "contract_monitor_subscribeOutput",
-  "type": "object"
-}New value: +null
  3. Changed7 schema fields changed
    • changedInput schema / properties / addresses / description
      Previous value: -"Up to 10 contract addresses"New value: +"Up to 10 0x-prefixed EVM addresses to watch"
    • removedInput schema / properties / durationDays
      Removed value: -{
-  "default": 30,
-  "title": "Durationdays",
-  "type": "integer"
-}
    • addedInput schema / properties / duration_days
      Added value: +{
+  "default": 30,
+  "description": "Subscription length in days (default 30; max per seller policy).",
+  "title": "Duration Days",
+  "type": "integer"
+}
    • changedInput schema / properties / thresholds / description
      Previous value: -"Optional thresholds object"New value: +"Optional JSON object for alert sensitivity (e.g. liquidity drop %, admin key moves). Omit or {} for seller defaults."
    • removedInput schema / properties / webhookUrl
      Removed value: -{
-  "description": "HTTPS webhook URL",
-  "title": "Webhookurl",
-  "type": "string"
-}
    • addedInput schema / properties / webhook_url
      Added value: +{
+  "description": "HTTPS URL that receives POST alerts when risk thresholds breach",
+  "title": "Webhook Url",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "addresses",
-  "webhookUrl"
-]New value: +[
+  "addresses",
+  "webhook_url"
+]
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Given annotations already set readOnly=false and idempotent=true, the description adds useful behavior: 30-day duration, webhook firing on specific risk events, and a maximum of 10 addresses. It avoids contradiction and fills in the 'side effect' of creating an active subscription.

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?

The description is two lean sentences with no filler. The action, constraints, and alert categories are all front-loaded or directly contextual.

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?

With a complete schema and these two sentences, an agent knows what action to take and effect to expect. But the tool lacks an output schema and the description does not explain the response shape, how repeated subscriptions are handled, or any payment/cancellation details.

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?

Input schema coverage is 100%, so baseline is 3. The description repeats the address limit already in the schema and only loosely trades thresholds to alert types. It does not add meaningful parameter semantics beyond the schema definitions.

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?

The description uses a specific verb ('Subscribe to') and names a precise resource: 30-day continuous monitoring of up to 10 EVM contract addresses. It lists concrete alert categories and clearly distinguishes this from one-time audit/triage siblings.

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 context is implied: the subscription product and alert categories suggest this is for continuous monitoring, not one-off analysis. However, it does explicitly say when to use this vs alternatives or when not to use it.

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