Skip to main content
Glama

Blackwood State

by io.github.Blackwood-State
OverviewDiscussionsAdmin

Crypto news

blackwood_crypto_news
Read-onlyIdempotent

Use when you need crypto news headlines about bitcoin, ethereum, a token or the crypto market from recent articles. Do not use for prices, full article text, social media posts or news older than 72 hours. Returns JSON with the latest crypto and blockchain news headlines from the last 72 hours (title, link, source, time, tone, people and organizations), from the GDELT global news graph for 0.005 USDC per call. Typical response time 1500 ms (p95). Category: Search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hoursNoHow far back to search, in hours (1-72, default 24)
limitNoMost articles to return (1-50, default 20), newest first
tokenNoNarrow to one coin, chain or company, e.g. solana, xrp or coinbase (any crypto news when omitted)
response_formatNoconcise (the default when omitted) keeps the JSON short: long fields such as base64 images or audio come back as separate image/audio content blocks and other long strings are cut with a marker; detailed returns the full JSON

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "articles": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "domain": {
-              "type": "string"
-            },
-            "image": {
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "organizations": {
-              "items": {
-                "type": "string"
-              },
-              "type": "array"
-            },
-            "persons": {
-              "items": {
-                "type": "string"
-              },
-              "type": "array"
-            },
-            "publishedAt": {
-              "type": "string"
-            },
-            "title": {
-              "type": "string"
-            },
-            "tone": {
-              "type": [
-                "number",
-                "null"
-              ]
-            },
-            "url": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "title",
-            "url",
-            "domain",
-            "publishedAt",
-            "tone",
-            "image",
-            "persons",
-            "organizations"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "attribution": {
-        "type": "string"
-      },
-      "count": {
-        "type": "number"
-      },
-      "hours": {
-        "type": "number"
-      },
-      "lastIngestAt": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "token": {
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "required": [
-      "token",
-      "hours",
-      "count",
-      "articles",
-      "lastIngestAt",
-      "attribution"
-    ],
-    "type": "object"
-  },
-  {
-    "description": "x402 PaymentRequired (returned with isError when payment is needed)",
-    "properties": {
-      "accepts": {
-        "items": {
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "error": {
-        "type": "string"
-      },
-      "extensions": {
-        "type": "object"
-      },
-      "resource": {
-        "type": "object"
-      },
-      "x402Version": {
-        "type": "integer"
-      }
-    },
-    "required": [
-      "x402Version",
-      "accepts"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "articles": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "domain": {
+              "type": "string"
+            },
+            "image": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "organizations": {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "persons": {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "publishedAt": {
+              "type": "string"
+            },
+            "title": {
+              "type": "string"
+            },
+            "tone": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "title",
+            "url",
+            "domain",
+            "publishedAt",
+            "tone",
+            "image",
+            "persons",
+            "organizations"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "attribution": {
+        "type": "string"
+      },
+      "count": {
+        "type": "number"
+      },
+      "hours": {
+        "type": "number"
+      },
+      "lastIngestAt": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "next": {
+        "additionalProperties": false,
+        "description": "Suggested next paid call in the same family (call it in a loop when the task continues)",
+        "properties": {
+          "method": {
+            "enum": [
+              "GET",
+              "POST"
+            ],
+            "type": "string"
+          },
+          "sample": {
+            "description": "Free fixed sample of the whole family",
+            "type": "string"
+          },
+          "service": {
+            "description": "Service id of the suggested next paid call",
+            "type": "string"
+          },
+          "tool": {
+            "description": "MCP tool name of the same call",
+            "type": "string"
+          },
+          "url": {
+            "description": "Paid route of the next call",
+            "type": "string"
+          },
+          "useWhen": {
+            "description": "When the next call is the right one",
+            "type": "string"
+          }
+        },
+        "required": [
+          "service",
+          "tool",
+          "method",
+          "url",
+          "useWhen",
+          "sample"
+        ],
+        "type": "object"
+      },
+      "token": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "token",
+      "hours",
+      "count",
+      "articles",
+      "lastIngestAt",
+      "attribution"
+    ],
+    "type": "object"
+  },
+  {
+    "description": "x402 PaymentRequired (returned with isError when payment is needed)",
+    "properties": {
+      "accepts": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "error": {
+        "type": "string"
+      },
+      "extensions": {
+        "type": "object"
+      },
+      "resource": {
+        "type": "object"
+      },
+      "x402Version": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "x402Version",
+      "accepts"
+    ],
+    "type": "object"
+  }
+]
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely new operational context: a per-call cost of 0.005 USDC, a p95 latency of 1500 ms, and the upstream source (the GDELT global news graph). That is exactly the kind of cost/latency/source disclosure an agent needs before calling a metered endpoint.

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?

Front-loaded with the use condition, immediately followed by the exclusion list, then the return shape, source, cost and latency in one dense sentence. No filler and every clause carries decision-relevant information.

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 an output schema present, return values need not be enumerated, yet the description still summarizes the payload (title, link, source, time, tone, people, organizations). Combined with cost, latency and source, an agent has everything needed to select and invoke this tool correctly.

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% with bounds, defaults and an enum all documented, so the schema does the heavy lifting and a baseline of 3 applies. The description adds the 72-hour horizon and the returned fields but no extra parameter syntax or semantics 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 names a specific verb and resource ('crypto news headlines about bitcoin, ethereum, a token or the crypto market from recent articles') and scopes it to a 72-hour window, which separates it from blackwood_news_search and the price-oriented siblings without requiring the agent to open a schema.

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 gives explicit when-to-use ('need crypto news headlines') and when-not-to-use conditions ('prices, full article text, social media posts or news older than 72 hours'), which map implicitly to blackwood_token_price and blackwood_webpage_markdown. The alternative tools are not named outright, so the routing requires a small inference.

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

All Blackwood State toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources