Industry Pulse

Search AI coding agent events

search_events

Read-onlyIdempotent

Search stored events by words. Use it for "what happened with Claude Code this week?", "any news about Gemini CLI?", "Codex releases". Pass q, words that must all appear in an event's title or summary. Optional: hours to look back (default 168, at most 720), limit (default 10, at most 25). Returns matching events ranked by score and heat, each with a summary, heat and source links, and the total number of matches.

Input Schema

Name	Required	Description
`q`	Yes	Words to look for in event titles and summaries, such as "claude code release". Every word must appear.
`hours`	No	Look back this many hours (default 168, at most 720)
`limit`	No	Most events returned (default 10)
`niche`	No	The topic area to read. Only "ai-coding-agents" (AI coding agents) exists today, and it is the default.

Output Schema

Name	Required	Description
`asOf`	Yes	When the sources were last read completely
`note`	Yes
`as_of`	Yes	ISO 8601 time the data was published by its source or fetched from it. A cached answer keeps the time of its fetch.
`niche`	Yes
`total`	Yes	Matching events before the limit was applied
`events`	Yes
`source`	Yes	Who the data comes from, to cite and to check it against.
`untrusted_source`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 23, 2026

addedInput schema / examples

Added value: +[
+  {
+    "hours": 168,
+    "q": "claude code"
+  }
+]

addedOutput schema / properties / as_of

Added value: +{
+  "description": "ISO 8601 time the data was published by its source or fetched from it. A cached answer keeps the time of its fetch.",
+  "type": "string"
+}

addedOutput schema / properties / source

Added value: +{
+  "description": "Who the data comes from, to cite and to check it against.",
+  "properties": {
+    "name": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "url"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / untrusted_source
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "niche",
-  "asOf",
-  "events",
-  "total"
-]New value: +[
+  "niche",
+  "asOf",
+  "events",
+  "total",
+  "untrusted_source",
+  "note",
+  "as_of",
+  "source"
+]

Changed1 schema field changedOct 5, 2026

removedOutput schema / properties / note_from_openkrill

Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, so the safety profile is covered. The description adds non-obvious behavior: default and maximum values for hours and limit, AND-semantics of the query words, ranking by score and heat, and the returned fields including total match count. It does not mention pagination or result ordering ties.

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?

Front-loaded with the core action and an illustrative use case, then constraints and return shape. The example questions earn their place by conveying usage, though they consume a fair share of the text for a short tool.

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?

An output schema exists, so return values need not be spelled out, yet the description still summarizes them helpfully. Combined with defaults, caps, and match semantics, an agent has enough to call it correctly; only the niche parameter goes undiscussed.

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%, so the schema already documents q, hours, and limit. The description largely restates those semantics (all words must appear, default 168, max 720, default 10, max 25) and says nothing about the fourth parameter, niche, so it adds little beyond the structured fields.

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?

States a specific verb and resource ("search stored events by words") and illustrates it with concrete example queries. It implicitly distinguishes itself from sibling latest_events by emphasizing word-based matching, but never names a sibling explicitly.

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?

The three quoted example questions ("what happened with Claude Code this week?", "any news about Gemini CLI?", "Codex releases") give a clear sense of the intended use context. There is no explicit when-not-to-use guidance or pointer to the alternative sibling tools like latest_events or daily_digest.

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

All Industry Pulse 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.