Skip to main content
Glama
Sign In

Warmth Engine Observatory

by com.warmthengine
OverviewDiscussionsAdmin

Search Events

search_events
Read-onlyIdempotent

Search and filter the WEO event corpus by query text or classification (bloc, tier, domain, event type, primary industry tag); returns the matching events with their metadata, capped by limit (default 20, max 50). Use to discover or shortlist events; for a single event's complete record, use get_event. Events enter after a verification lag from their implementation date (six months; 60 days for verified product releases), so recent events may not yet appear, and an empty result is not evidence that no such event has occurred. Free tier returns the classification facts with the deeper assessment and evidence withheld on non-sample events; full tier — and sample events on either tier — return every field.

Input Schema

NameRequiredDescriptionDefault
blocNoFilter by bloc: Western, Eastern (tier 3); Western-Led, Eastern-Led (tier 2); Cross-Bloc (tier 1). Each bloc value occurs at one tier only
tierNoFilter by tier: 1 (Cross-Bloc), 2 (Between-Bloc), 3 (Intra-Bloc); each tier carries its own bloc values (see `bloc`)
typeNoFilter by event type: Policy, Infrastructure, Corporate, Coordination
limitNoNumber of results (default 20, max 50)
queryNoFree-text search across event name and description
domainNoFilter by domain: Technology, Energy/Infrastructure, Security, Trade
industryNoFilter by primary industry tag

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / bloc / enum
      Added value: +[
+  "Western",
+  "Eastern",
+  "Western-Led",
+  "Eastern-Led",
+  "Cross-Bloc"
+]
    • addedInput schema / properties / domain / enum
      Added value: +[
+  "Technology",
+  "Energy/Infrastructure",
+  "Security",
+  "Trade"
+]
    • addedInput schema / properties / industry / enum
      Added value: +[
+  "Semiconductors & Equipment",
+  "Cloud, Data Centres & Connectivity Infrastructure",
+  "AI Software & Platforms",
+  "Defence & Aerospace",
+  "Energy & Power Infrastructure",
+  "Financial Services & Investment",
+  "Mining & Critical Minerals",
+  "Trade & Logistics",
+  "Automotive & Manufacturing",
+  "Quantum Computing Infrastructure",
+  "Telecoms"
+]
    • addedInput schema / properties / tier / enum
      Added value: +[
+  1,
+  2,
+  3
+]
    • removedInput schema / properties / tier / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / tier / minimum
      Removed value: --9007199254740991
    • changedInput schema / properties / tier / type
      Previous value: -"integer"New value: +"number"
    • addedInput schema / properties / type / enum
      Added value: +[
+  "Policy",
+  "Infrastructure",
+  "Corporate",
+  "Coordination"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / bloc / description
      Previous value: -"Filter by bloc: Western, Eastern, Western-Led, Eastern-Led, Cross-Bloc"New value: +"Filter by bloc: Western, Eastern (tier 3); Western-Led, Eastern-Led (tier 2); Cross-Bloc (tier 1). Each bloc value occurs at one tier only"
    • changedInput schema / properties / tier / description
      Previous value: -"Filter by tier: 1, 2, or 3"New value: +"Filter by tier: 1 (Cross-Bloc), 2 (Between-Bloc), 3 (Intra-Bloc); each tier carries its own bloc values (see `bloc`)"
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  4. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Keyword search across event name and description"New value: +"Free-text search across event name and description"
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent, closed-corpus read, so the bar is lower, yet the description still adds substantive behavior no structured field carries: the verification lag (six months; 60 days for verified product releases) and the tier-dependent field availability (free tier withholds assessment/evidence on non-sample events). These are real behavioral traits an agent must know to interpret results.

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 purpose and return shape, then routing, then the lag caveat and tier behavior — every sentence carries information and none is filler. It is dense and slightly long for a single paragraph, but not padded, so it sits just under a perfect mark.

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?

There is no output schema, and the description compensates by describing what is returned (matching events plus metadata, bounded by `limit`), how completeness is constrained (verification lag), and how results differ by tier. Nothing essential for correct invocation or result interpretation 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% and all seven parameters, including the five enums, are documented in the schema itself with cross-references between `bloc` and `tier`. The description restates the filter names and the limit default/max but adds no syntax, format, or combination semantics beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Search and filter the WEO event corpus') and enumerates the filter dimensions (bloc, tier, domain, event type, industry tag) plus the return shape (matching events with metadata, capped by limit). It also explicitly distinguishes itself from the sibling `get_event`, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use ('discover or shortlist events') and names the alternative and its condition ('for a single event's complete record, use get_event'). It goes further by warning that a recent event may be absent due to the verification lag and that an empty result is not evidence of non-occurrence, which is exactly the kind of usage guidance that prevents misinterpretation.

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

All Warmth Engine Observatory 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