Skip to main content
Glama

tauri_ipc_get_captured

Read-only

Retrieve captured IPC traffic from Tauri applications to monitor invoke calls and events with arguments and responses. Requires ipc_monitor to be active.

Instructions

[Tauri Apps Only] Get captured Tauri IPC traffic (requires ipc_monitor started). Shows captured commands (invoke calls) and events with arguments and responses. For browser network requests, use Chrome DevTools MCP instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoFilter events by command name
appIdentifierNoApp port or bundle ID to target. Defaults to the only connected app or the default app if multiple are connected.

Implementation Reference

  • The handler function `getIPCEvents` that implements the core logic: invokes the Tauri plugin command to retrieve captured IPC events, applies optional filtering, and returns formatted JSON.
    export async function getIPCEvents(filter?: string, appIdentifier?: string | number): Promise<string> {
       try {
          const result = await executeIPCCommand({ command: 'plugin:mcp-bridge|get_ipc_events', appIdentifier });
    
          const parsed = JSON.parse(result);
    
          if (!parsed.success) {
             throw new Error(parsed.error || 'Unknown error');
          }
    
          let events = parsed.result;
    
          if (filter && Array.isArray(events)) {
             events = events.filter((e: unknown) => {
                const event = e as { command?: string };
    
                return event.command && event.command.includes(filter);
             });
          }
    
          return JSON.stringify(events);
       } catch(error: unknown) {
          const message = error instanceof Error ? error.message : String(error);
    
          throw new Error(`Failed to get IPC events: ${message}`);
       }
    }
  • Zod schema `GetIPCEventsSchema` defining input validation for the tool: optional `filter` string and `appIdentifier`.
    export const GetIPCEventsSchema = z.object({
       filter: z.string().optional().describe('Filter events by command name'),
       appIdentifier: z.union([ z.string(), z.number() ]).optional().describe(
          'App port or bundle ID to target. Defaults to the only connected app or the default app if multiple are connected.'
       ),
    });
  • Tool registration in the central `TOOLS` registry array, linking name, description, schema, annotations, and handler.
    {
       name: 'tauri_ipc_get_captured',
       description:
          '[Tauri Apps Only] Get captured Tauri IPC traffic (requires ipc_monitor started). ' +
          'Shows captured commands (invoke calls) and events with arguments and responses. ' +
          'For browser network requests, use Chrome DevTools MCP instead.',
       category: TOOL_CATEGORIES.IPC_PLUGIN,
       schema: GetIPCEventsSchema,
       annotations: {
          title: 'Get Captured IPC Traffic',
          readOnlyHint: true,
          openWorldHint: false,
       },
       handler: async (args) => {
          const parsed = GetIPCEventsSchema.parse(args);
    
          return await getIPCEvents(parsed.filter, parsed.appIdentifier);
       },
    },
Behavior4/5

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

Annotations provide readOnlyHint=true and openWorldHint=false, indicating a safe, constrained read operation. The description adds valuable context beyond annotations: it specifies prerequisites ('requires ipc_monitor started'), clarifies what data is returned ('captured commands and events with arguments and responses'), and mentions a dependency on app connectivity. No contradiction with annotations exists.

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?

The description is front-loaded with key information in two efficient sentences. Every sentence earns its place: the first states purpose and prerequisites, the second clarifies scope and alternatives. No wasted words, and structure guides the agent effectively.

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?

Given the tool's complexity (monitoring IPC traffic), annotations cover safety (read-only), and schema fully documents parameters, the description is mostly complete. It lacks details on output format (no output schema) and potential limitations like data volume or real-time aspects, but covers prerequisites, scope, and alternatives well.

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 the schema fully documents both parameters. The description does not add any parameter-specific information beyond what's in the schema (e.g., it doesn't explain filter syntax or appIdentifier defaults in more detail). Baseline 3 is appropriate when schema handles parameter documentation.

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 specific action ('Get captured Tauri IPC traffic'), the resource ('captured commands and events'), and scope ('requires ipc_monitor started'). It explicitly distinguishes from sibling tools by mentioning 'For browser network requests, use Chrome DevTools MCP instead,' which differentiates it from webview-related siblings.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: it specifies when to use ('[Tauri Apps Only]', 'requires ipc_monitor started'), when not to use ('For browser network requests, use Chrome DevTools MCP instead'), and mentions an alternative tool by name. This gives clear context for tool selection among siblings.

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/hypothesi/mcp-server-tauri'

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