Skip to main content
Glama

check_consequences

Retrieve events linked to agent actions or recent activity to monitor outcomes and feedback in real-time.

Instructions

Get events associated with an agent action, or all recent events

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
action_idNoAction ID to filter by (optional — omit for all recent)

Implementation Reference

  • The handler function 'handleCheckConsequences' that implements the 'check_consequences' tool logic.
    private async handleCheckConsequences(args: Record<string, unknown>) {
      const schema = z.object({ action_id: z.string().optional() });
      const parsed = schema.parse(args);
    
      const events = parsed.action_id
        ? getEventsByActionId(parsed.action_id)
        : getRecentEvents(50);
    
      return {
        content: [{
          type: 'text' as const,
          text: JSON.stringify(events, null, 2),
        }],
      };
    }
  • src/server.ts:133-137 (registration)
    The tool registration of 'check_consequences' in the server definition.
    name: 'check_consequences',
    description: 'Get events associated with an agent action, or all recent events',
    inputSchema: {
      type: 'object',
      properties: {
Behavior2/5

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

No annotations are provided, so the description carries full disclosure burden. It does not specify what constitutes 'recent' (time window), whether events are consumed/destructively read, or the return format. 'Get' implies read-only but lacks explicit safety confirmation.

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?

Single sentence efficiently covers both use cases. Front-loaded with the verb 'Get'. However, given the lack of annotations and output schema, the brevity may be excessive—slightly more detail would improve utility without sacrificing clarity.

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

Completeness3/5

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

Covers the basic input contract adequately given the single optional parameter. However, without an output schema or annotations, the description should have disclosed behavioral traits like time windows for 'recent', pagination, or event lifecycle (consumed vs. peeked).

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?

With 100% schema coverage, the baseline is 3. The description adds valuable semantic context by explaining the two invocation modes: when 'action_id' is provided vs. omitted ('all recent'), effectively documenting the parameter's behavioral impact beyond the schema definition.

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?

Uses specific verb 'Get' and resource 'events'. Clearly delineates the dual scope: specific 'agent action' vs 'all recent events'. However, it fails to explicitly distinguish from sibling 'poll_events', leaving ambiguity about the retrieval mechanism.

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?

Describes the two operational modes (filtered vs unfiltered) but provides no explicit guidance on when to use each, and fails to mention sibling alternatives like 'poll_events' or when to prefer this over other watch-related tools.

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/jarvisassistantux/loopsense'

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