Skip to main content
Glama

Warmth Engine Observatory

by com.warmthengine

search_events

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. 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

TableJSON Schema
NameRequiredDescriptionDefault
blocNoFilter by bloc: Western, Eastern, Western-Led, Eastern-Led, Cross-Bloc
tierNoFilter by tier: 1, 2, or 3
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

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses important tier-dependent behavior: free tier returns classification facts but withholds deeper assessment and evidence on non-sample events, while full tier and sample events return every field. It also discloses the limit cap.

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 two dense sentences with no filler. It front-loads the purpose and filter options, then adds usage guidance and tier-specific behavior. Every sentence earns its place.

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?

The description covers search scope, filter dimensions, result cap, usage context, the alternative for full single-event records, and tier-based return differences. Given the rich parameter schema and no output schema, this is sufficient for an agent to select and invoke the 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%, so the schema already documents all seven parameters. The description adds useful framing by grouping parameters into query text and classification, but it does not materially extend the semantic meaning beyond what the schema provides.

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 clearly states the verb 'Search and filter' and the resource 'WEO event corpus', then enumerates the filter dimensions: query text, bloc, tier, domain, event type, and primary industry tag. It also explicitly differentiates itself from get_event by positioning search_events as the discovery/shortlisting tool.

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?

The description gives an explicit decision rule: 'Use to discover or shortlist events; for a single event's complete record, use get_event.' This names the sibling alternative and states the condition for choosing one over the other.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool targets a distinct data slice or operation. For example, `get_actors` retrieves full actor profiles while `query_scp` offers pivoting and comparison; `search_events` finds event IDs and `get_event` retrieves a full record; `get_threads` provides material links separate from `traverse_coordination` for lineage walks. There is no overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent `verb_noun` pattern with underscore separators. Most use `get_` for retrieval, with `query_scp`, `search_events`, and `traverse_coordination` using different verbs that accurately reflect their distinct actions. The naming is predictable and intuitive.

Tool Count5/5

16 tools is well-scoped for the complexity of an observation platform that covers actors, blocs, events, connections, topology, vocabulary, statistics, and material links. Each tool earns its place by covering a necessary query pattern without unnecessary fragmentation.

Completeness5/5

The tool set provides comprehensive coverage of the domain: actor retrieval and querying (profiles, comparisons, watch), bloc membership, event discovery and full records, connection traversal and filtering, structural topology, material links, vocabulary lookups, and summary statistics. No obvious gaps in read access are present.

Resources