whale-data

My fired alerts

my_alerts

Read-onlyIdempotent

What your CoinLobster alerts fired since a time, newest first, with the move since each. Needs a signed-in connection (free).

Input Schema

TableJSON Schema

Name	Required	Description
`coin`	No	Coin symbol, e.g. BTC. A pair like ETH/USD works too.
`cursor`	No	Next page: the cursor from the previous answer.
`detail`	No	brief (default): the answer, key numbers and top rows. full: every row, paged with cursor.
`since_ms`	No	Only rows newer than this Unix-ms time (polling cursor).

Output Schema

TableJSON Schema

Name	Required	Description
`as_of`	No	Data time, ISO.
`caveat`	No	A real limit, when non-null.
`cursor`	No	Next page (detail full).
`delayed`	No	Set when not live.
`summary`	No	The answer in one sentence.
`as_of_ms`	No	Data time, Unix ms.
`available`	No	False: no data; note says why.
`truncated`	No	Rows held back; see trimmed.
`next_tools`	No	Follow-up calls {tool,args,why}.
`access_note`	No	What this connection could not return.

Schema Changelog

Changes observed during successful MCP inspections.

Changed28 schema fields changedSep 24, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +{}
```

changedInput schema / properties / coin / description

Previous value: -"Only alerts on this coin. Omit for every coin."New value: +"Coin symbol, e.g. BTC. A pair like ETH/USD works too."

addedInput schema / properties / cursor

Added value: +{
+  "description": "Next page: the cursor from the previous answer.",
+  "type": "string"
+}

addedInput schema / properties / detail

Added value: +{
+  "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor.",
+  "enum": [
+    "brief",
+    "full"
+  ],
+  "type": "string"
+}

removedInput schema / properties / pair

Removed value: -{
-  "description": "Alias for coin.",
-  "type": "string"
-}

changedInput schema / properties / since_ms / description

Previous value: -"Only alerts fired after this Unix-ms timestamp. Defaults to the last 24 hours. Pass back next_since_ms from the previous answer to read only what is new."New value: +"Only rows newer than this Unix-ms time (polling cursor)."

removedInput schema / properties / since_ms / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / since_ms / minimum
```
Removed value: --9007199254740991
```

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedOutput schema / properties / access_note

Added value: +{
+  "description": "What this connection could not return."
+}

removedOutput schema / properties / alerts

Removed value: -{
-  "anyOf": [
-    {
-      "items": {},
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Starter and up: fired_at, type, coin, pair, side, usd, price_at_fire, exchange, wallet, since_pct."
-}

addedOutput schema / properties / as_of

Added value: +{
+  "description": "Data time, ISO."
+}

addedOutput schema / properties / as_of_ms

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Data time, Unix ms."
+}

removedOutput schema / properties / available / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

changedOutput schema / properties / available / description

Previous value: -"False keyless (reason no_owner: sign in, free) or when history is not wired."New value: +"False: no data; note says why."

addedOutput schema / properties / available / type
```
Added value: +"boolean"
```

addedOutput schema / properties / caveat

Added value: +{
+  "description": "A real limit, when non-null."
+}

removedOutput schema / properties / coins

Removed value: -{
-  "anyOf": [
-    {
-      "items": {},
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Per coin: coin, fired."
-}

addedOutput schema / properties / cursor

Added value: +{
+  "description": "Next page (detail full)."
+}

addedOutput schema / properties / delayed

Added value: +{
+  "description": "Set when not live."
+}

removedOutput schema / properties / fired

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Alerts that fired since since_ms."
-}

removedOutput schema / properties / next_since_ms

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Pass back as since_ms to read only what is new."
-}

addedOutput schema / properties / next_tools

Added value: +{
+  "description": "Follow-up calls {tool,args,why}.",
+  "items": {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / rows_withheld

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Free: rows held back (the counts above are complete)."
-}

changedOutput schema / properties / summary / description

Previous value: -"The answer in one plain sentence, computed from the fields below. Open the reply with this, then let the numbers back it up. Null only when there was nothing to summarise."New value: +"The answer in one sentence."

addedOutput schema / properties / truncated

Added value: +{
+  "description": "Rows held back; see trimmed."
+}

removedOutput schema / properties / upgrade

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": {},
-      "propertyNames": {
-        "type": "string"
-      },
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Present only when rows were withheld: the cheapest plan that returns them."
-}

AddedSep 5, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that a signed-in connection is needed and that it returns alerts that have 'fired' since a time, which is useful context. However, it does not elaborate on pagination behavior or response structure, but with annotations and an output schema present, the description adds sufficient supplementary 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 a single sentence, front-loaded with the main function, and includes the key prerequisite (signed-in connection). Every word earns its place; no fluff or redundancy.

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?

Given the output schema exists, the annotations cover safety, and the schema documents all parameters, the description is fairly complete. It covers the core behavior, sorting, and the time constraint. The main gap is lack of usage guidance to differentiate from sibling tools, but that is addressed under usage_guidelines. Overall, an agent can call this tool correctly based on the information provided.

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% – every parameter has a description in the schema. The description itself only mentions 'since a time', which mirrors the since_ms parameter, but adds no new meaning beyond the schema. The baseline of 3 is appropriate because the schema handles parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear purpose: list fired alerts since a time, sorted newest first, with the move since each. It uses a specific verb ('fired') and resource (alerts), and is not a tautology. However, it does not explicitly distinguish itself from sibling alert-related tools like 'signals' or 'watchlist_brief', though the phrase 'fired alerts' gives some distinction.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. It mentions the requirement for a signed-in connection, but does not state under what circumstances an agent should choose this over other alert/notification tools. No exclusions or alternative tool names are provided.

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

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