Skip to main content
Glama
heznpc

iconnect-mcp

by heznpc
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

Event Monitor Status

event_status
Read-onlyIdempotent

Verify whether real-time event monitoring is currently active.

Instructions

Check if real-time event monitoring is active.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/server/mcp-setup.ts:392-403 (registration)
    Registration of the 'event_status' tool using lServer.registerTool(). The tool checks if real-time event monitoring is active via eventBus.isRunning.
    lServer.registerTool(
  "event_status",
  {
    title: "Event Monitor Status",
    description: "Check if real-time event monitoring is active.",
    inputSchema: {},
    annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false },
  },
  async () => {
    return ok({ running: eventBus.isRunning });
  },
);
  • src/server/mcp-setup.ts:400-402 (handler)
    Handler function for event_status: returns { running: eventBus.isRunning } to indicate whether the event bus is active.
    async () => {
  return ok({ running: eventBus.isRunning });
},
  • src/server/mcp-setup.ts:394-398 (schema)
    Input/output schema for event_status: empty inputSchema, with annotations indicating read-only, non-destructive, idempotent behavior.
    {
  title: "Event Monitor Status",
  description: "Check if real-time event monitoring is active.",
  inputSchema: {},
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false },

Tool Definition Quality

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds no further behavioral details beyond what is stated, missing specifics like what 'active' means or return format. It does not contradict annotations.

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?

Description is a single 6-word sentence, perfectly concise and front-loaded. No wasted words.

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?

Despite no output schema, the description is sufficient for a simple boolean status check. It covers the essential purpose, though could mention what the output indicates (e.g., boolean). Given the low complexity, it is almost complete.

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

Parameters4/5

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

Tool has zero parameters, so schema description coverage is 100%. Description adds no parameter info, but baseline is 4 per guidelines. No additional meaning is needed.

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 tool checks if real-time event monitoring is active, using specific verb 'check' and resource 'event monitoring status'. It distinguishes from siblings like event_subscribe or list_events, which serve different purposes.

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 implies usage context (checking monitoring status) but does not explicitly state when to use or avoid this tool. For a simple status check, the context is clear, but no alternatives or exclusions are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/heznpc/AirMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server