Skip to main content
Glama

Public record feed

muhabbit_events
Read-only

The public record: every headline Muhabbit published, newest first. Each item is an entry of the hash-chained public record with three timestamps in UTC ms (source_at = publisher, detected_at = our ingest, published_at = our publication), focus tags, a category and impact 0-100. Covers exchange listings, US CPI, jobs and Fed, crypto, macro and tech. Exchange security alert headlines appear here too (suspected ones start with 'Unconfirmed:'; their evidence is in muhabbit_alerts). Page with next_cursor. (Free: no credentials needed.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "muhabbit_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoEvents per page, 1-20 (default 20)
cursorNonext_cursor from the previous page
categoriesNoKeep only these categories: listings (exchange listings), cpi, jobs, fed (US macro prints), crypto, macro, tech
min_impactNoKeep events with impact at or above this (0-100). Above 0 drops events whose impact is unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and closed-world, so safety is covered; the description adds genuinely new behavior: newest-first ordering, hash-chained entries, the 'Unconfirmed:' naming convention for suspected alerts, and that no credentials are required. It stops short of rate limits or page-size behavior beyond the schema.

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?

A single dense paragraph that is front-loaded with the resource and ordering before field semantics and the sibling pointer. Nearly every clause carries information; the timestamp-triplet explanation is the longest stretch but is load-bearing given there is no output schema.

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?

With no output schema, the description carries the return-shape burden and does so: three UTC-ms timestamps with their meanings, focus tags, category and a 0-100 impact. Free/no-credentials is noted and the alerts cross-reference is given; only rate limits and page-size defaults are missing, and defaults live in the schema.

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 limit, cursor, categories and min_impact are already fully documented. The description reinforces cursor paging and enumerates the topical coverage that maps to the categories enum, but adds no syntax or filtering subtlety beyond the schema.

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 resource and scope: 'every headline Muhabbit published, newest first', and identifies the payload as hash-chained public record entries. It is distinguishable from muhabbit_news and muhabbit_record_entries by the record/hash-chain framing, though it never names those siblings to make the boundary explicit.

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

Usage Guidelines3/5

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

Gives operational guidance for paging ('Page with next_cursor') and routes 'Unconfirmed:' exchange security headlines to muhabbit_alerts for evidence. It never says when to prefer muhabbit_news, muhabbit_search or muhabbit_record_entries instead, so the usage boundary is implied rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources