Skip to main content
Glama

mu

by mu.micro

Browse stream

stream_list
Read-onlyIdempotent

Read what has happened here recently

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many entries to return (default 20, max 100)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"How many events to return (default 20, max 100)"New value: +"How many entries to return (default 20, max 100)"
  2. Changed1 schema field changed
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "How many events to return (default 20, max 100)",
+  "type": "number"
+}
  3. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds no new behavioral context. It doesn't mention ordering, time window, pagination behavior, or what 'recently' means, leaving the agent without useful operational details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words, but it is too terse to be informative. Conciseness at the expense of necessary detail is under-specification, not good structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (1 optional param, no output schema) and available annotations, the description still fails to explain what a stream is or what kind of events are shown. With many similar sibling tools, this lack of context makes it incomplete.

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 coverage is 100% because the only parameter 'limit' is described in the schema. The description adds no parameter-specific details, so it neither compensates nor detracts; the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Read what has happened here recently' uses a verb and implies a stream, but 'here' is undefined and it doesn't clarify what type of stream or content is listed. It fails to distinguish this from numerous sibling list tools like news_list, social_list, or recall_list.

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

Usage Guidelines2/5

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

No guidance is provided on when to use stream_list versus alternatives. There are no exclusions, prerequisites, or context clues to help an agent choose this tool over other list or read tools.

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

All mu 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

A3.6/5.0
Disambiguation5/5

Every tool is prefixed with a clear domain (e.g., apps_, blog_, transit_), and the suffix identifies a distinct action or resource. Overlapping tools like archive_search and news_search are explicitly differentiated in their descriptions.

Naming Consistency4/5

All tools consistently use a domain_prefix_suffix pattern, but the suffix is sometimes a verb (create, list, search) and sometimes a noun (inbox, status, address). This minor mixing prevents a perfect score but remains predictable and readable.

Tool Count2/5

With 113 tools, the count is far beyond the typical well-scoped range, even for a broad personal assistant. While each tool is distinct and serves a purpose, the sheer number is overwhelming and could be better organized into separate domain-specific servers.

Completeness4/5

Each domain has near-complete lifecycle coverage, including CRUD and search where relevant, with only minor gaps such as missing apps_delete or events_update. The wide range of covered domains itself demonstrates strong completeness for a general assistant.

Resources