whale-insights

sentiment_monthly

Read-onlyIdempotent

Social sentiment permanent monthly archive — Returns the permanent monthly archive of social sentiment per token — one row per token per calendar month, aggregated from daily snapshots before purge. Never deleted; covers 35 tracked tokens. Optional ?symbol=BTC to filter by token. Each row includes: month, symbol, avgScore (0–100), dominantSentiment (bullish/neutral/bearish), daysInMonth. Months with fewer than 20 daily records are excluded. No authentication required. 60 req/min. 5-min cache. — Use this for long-term monthly archive data; use the corresponding live or daily-history tool for current or finer-grained data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`symbol`	No	Token symbol to filter by (e.g. BTC, ETH). Omit to return all 35 tokens.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	No
`months`	No
`symbol`	No
`updatedAt`	No
`dataSource`	No
`attribution`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "attribution": {
+      "$ref": "#/components/schemas/Attribution"
+    },
+    "dataSource": {
+      "type": "string"
+    },
+    "months": {
+      "items": {
+        "properties": {
+          "avgScore": {
+            "type": "number"
+          },
+          "daysInMonth": {
+            "type": "integer"
+          },
+          "dominantSentiment": {
+            "type": "string"
+          },
+          "month": {
+            "format": "date",
+            "type": "string"
+          },
+          "symbol": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "symbol": {
+      "nullable": true,
+      "type": "string"
+    },
+    "total": {
+      "type": "number"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJun 26, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations' safety hints, the description discloses data lineage ('aggregated from daily snapshots before purge', 'Never deleted'), coverage ('35 tracked tokens'), an exclusion threshold ('fewer than 20 daily records'), and operational constraints ('No authentication required. 60 req/min. 5-min cache'). This is substantial added context.

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 dense yet each sentence adds distinct value: core function, aggregation source, retention, coverage, filter, output columns, exclusion rule, auth/rate/cache, and usage routing. The main purpose is front-loaded before the technical details.

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?

With one optional parameter, an output schema, and safety annotations already present, the description covers the only remaining contextual decisions an agent needs: long-term vs live/daily use, output row shape, coverage, and operational limits. Nothing essential is missing.

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%: the schema already documents the optional symbol filter, examples, and the 'omit to return all 35 tokens' behavior. The description repeats the optional ?symbol=BTC example but adds little new parameter-level meaning beyond the schema.

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 opens with 'Returns the permanent monthly archive of social sentiment per token' and specifies the row granularity ('one row per token per calendar month'), making the verb, resource, and scope unambiguous. It also distinguishes itself from sibling tools by labeling this the permanent monthly archive versus live or daily-history alternatives.

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?

It explicitly states when to choose this tool: 'Use this for long-term monthly archive data; use the corresponding live or daily-history tool for current or finer-grained data.' This gives clear use cases, but it does not name specific sibling tool IDs, leaving some identification to the agent.

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

All whale-insights 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?