MAD Synapse

pump.fun market pulse

pump_pulse

Read-onlyIdempotent

Live pump.fun heartbeat: trades/min, launches, graduations, graduation rate, hottest tokens in the last 15 min. Computed from our own live recording of every pump.fun bonding-curve trade. Use it to decide whether the launch market is hot or dead before scanning individual tokens. When to use: For the market right now; for trends over days use pump_history (callable here by name). Price: free. Errors: returns isError with a message for invalid input or an upstream failure (not charged).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`as_of`	No
`sol_usd`	No
`coverage`	No
`last_24h`	No
`last_hour`	No
`hottest_15m`	No
`trades_per_min`	No
`recent_graduations`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "as_of": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "coverage": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "hottest_15m": {
+      "items": {
+        "properties": {
+          "buy_sol": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "mint": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "net_sol": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "sell_sol": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "symbol": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "trades": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "wallets": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "type": "array"
+    },
+    "last_24h": {
+      "properties": {
+        "graduation_rate_pct": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "graduations": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "launches": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "last_hour": {
+      "properties": {
+        "active_tokens": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "graduations": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "launches": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "sol_volume": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "trades": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "unique_wallets": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "recent_graduations": {
+      "items": {
+        "properties": {
+          "graduated_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "mint": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "symbol": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "type": "array"
+    },
+    "sol_usd": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "trades_per_min": {
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 25, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With annotations already covering read-only, open-world, idempotent, and non-destructive behavior, the description adds meaningful context beyond annotations: it discloses the data source ('our own live recording of every pump.fun bonding-curve trade'), the cost ('Price: free'), and error behavior ('returns isError... not charged').

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?

The description is front-loaded with the core metrics and data source, then usage, price, and errors. It is slightly longer than necessary because the 'Use it to decide...' sentence overlaps with the following 'When to use' sentence, but no sentence is purely wasteful.

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

Completeness5/5

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

For a no-parameter, read-only tool with an output schema and rich annotations, the description is complete: it explains the metric window, data provenance, use case, alternative tool, cost, and error handling. Return-value structure is appropriately left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so parameter semantics are not applicable; the baseline of 4 applies. The description does not need to explain parameters because the schema is empty and fully documented.

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 states a specific resource (pump.fun market pulse) and enumerates the exact metrics returned: trades/min, launches, graduations, graduation rate, and hottest tokens over a 15-minute window. It also distinguishes itself from alternatives by naming pump_history for longer-term trends.

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?

It gives explicit when-to-use guidance: 'Use it to decide whether the launch market is hot or dead before scanning individual tokens' and 'When to use: For the market right now; for trends over days use pump_history.' The alternative and its selection condition are both stated.

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

All MAD Synapse tools Inspect

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

Need Help?