Skip to main content
Glama
Sign In
duddy

duddy

by qu15501267889-sketch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

duddy_events

Retrieve recent event stream to diagnose missing responses, such as popups not appearing or frontend callbacks not reporting.

Instructions

最近的事件流，排查「为什么没反应」时用（弹窗没弹、前端没回报等）。

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": "duddy_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
prefixNoduddy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, but it only says the events are 'recent' – no time window, ordering, volume cap, or whether the stream is a snapshot versus a live tail. It also doesn't disclose the read-only nature or the cost/rate implications of pulling events, leaving an agent with no basis for predicting behavior.

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?

One compact sentence with the resource front-loaded and a parenthetical of example symptoms; nothing is wasted. It is arguably too terse rather than too long, but the structure itself is clean.

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?

With no annotations, no output schema, and 0% parameter documentation, the description has to do all the work and does not. An agent knows roughly why to call it but not what it will get back (event shape), how far back 'recent' reaches, or how the prefix and limit affect results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters, and the description never mentions them. The default prefix of "duddy." silently scopes which events are returned and limit (default 30) controls how far back the agent looks – both are consequential and completely unexplained, so the description fails to compensate for the schema gap.

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?

"最近的事件流" names a specific resource (an event stream) and the scenario it serves (diagnosing 'why is there no response'). It is clear what the tool returns, but it never distinguishes itself from the overlapping sibling duddy_get_logs, which an agent could easily pick instead.

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 description gives an explicit trigger condition with concrete symptoms (popup did not appear, frontend did not report back), which is real when-to-use guidance. It stops short of naming exclusions or the alternative diagnostic siblings (duddy_get_logs, duddy_run_status, duddy_canvas_state), which is the main gap.

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

Deploy Server

Other Tools