Agent Einstein — Crypto & Market Intelligence

Token Social Hype

get_social_hype

Read-onlyIdempotent

Tokens ranked by social buzz over the last 24 hours, each with a sentiment classification (Positive/Negative/Neutral), the number of distinct KOL accounts discussing it, and a one-line summary of what is actually being said. BSC. Use when asked what is being talked about, what is trending socially, or how sentiment sits on a token.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Rows to return (1-15).
`sentiment`	No	Filter to one sentiment class.	All

Output Schema

TableJSON Schema

Name	Required	Description
`rows`	No	Tokens ranked by social hype.
`chain`	No	Chain the screen ran on.
`object`	No	Always "social-hype".
`reason`	No	Why the payload is absent, when `available` is false.
`available`	No	False when this call has no data — a snapshot that is not warm yet, a domain switched off, or an argument that was rejected. NOT an error, and NOT a statement about the market.
`sentiment`	No	Sentiment filter applied.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "available": {
+      "description": "False when this call has no data — a snapshot that is not warm yet, a domain switched off, or an argument that was rejected. NOT an error, and NOT a statement about the market.",
+      "type": "boolean"
+    },
+    "chain": {
+      "description": "Chain the screen ran on."
+    },
+    "object": {
+      "description": "Always \"social-hype\"."
+    },
+    "reason": {
+      "description": "Why the payload is absent, when `available` is false.",
+      "type": "string"
+    },
+    "rows": {
+      "description": "Tokens ranked by social hype.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "chainId": {
+            "description": "EVM chain id."
+          },
+          "contractAddress": {
+            "description": "Token contract."
+          },
+          "kolCount": {
+            "description": "Distinct known accounts posting."
+          },
+          "marketCapUsd": {
+            "description": "Market cap in USD."
+          },
+          "priceChangePct": {
+            "description": "Percentage price change over the period."
+          },
+          "sentiment": {
+            "description": "Sentiment read for this token."
+          },
+          "socialHype": {
+            "description": "Hype score — what the ranking is on."
+          },
+          "summaryBrief": {
+            "description": "One-line summary of what is being said."
+          },
+          "summaryDetail": {
+            "description": "Longer summary."
+          },
+          "symbol": {
+            "description": "Token symbol."
+          },
+          "tokenAgeMs": {
+            "description": "Token age in milliseconds."
+          }
+        }
+      },
+      "type": "array"
+    },
+    "sentiment": {
+      "description": "Sentiment filter applied."
+    }
+  },
+  "type": "object"
+}

AddedAug 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds valuable behavioral context: the time window (24 hours), the data composition (sentiment, KOL count, summary), and the network (BSC). It does not contradict annotations and provides meaningful additional detail.

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 concise and well-structured, front-loading the core function (ranking by social buzz) before detailing output and usage. No wasted words; every clause serves a purpose, making it easy for an agent to parse quickly.

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?

The description covers the tool's purpose, output details, network, and usage guidance. Since an output schema exists, the absence of explicit return format details is acceptable. It is complete enough for an agent to call correctly, with only minor gaps like pagination or edge cases that are typically not required.

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 coverage is 100%, so both parameters are already described in the schema. The tool description reinforces the sentiment parameter by mentioning sentiment classification, but does not add new semantic meaning beyond what the schema provides. Baseline of 3 is appropriate.

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 clearly states the tool's function: it ranks tokens by social buzz over the last 24 hours, specifying the output fields (sentiment, KOL count, summary) and the network (BSC). It distinguishes itself from siblings like get_market_sentiment by focusing on social buzz and KOL discussions, making it easily identifiable.

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

Usage Guidelines4/5

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

Explicit usage directions are given: 'Use when asked what is being talked about, what is trending socially, or how sentiment sits on a token.' It does not name alternatives or state when not to use it, but the conditions are clear and the BSC scope further narrows applicability, making it a strong, though not exhaustive, guideline.

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

All Agent Einstein — Crypto & Market Intelligence 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.