Skip to main content
Glama
Sign In
fuzzmind-frida-mcp

fuzzmind-frida-mcp

by fuzzmind
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

frida_session_get_events

Retrieve lifecycle events from a Frida session to monitor its activity. Optionally clear events or set a limit on the number returned.

Instructions

Read lifecycle events for a persistent Frida session.

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

Input Schema

NameRequiredDescriptionDefault
session_idNo
clearNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description should fully disclose behavior. It only states 'Read', but doesn't mention if events are cleared after reading (implied by the 'clear' parameter), side effects, or idempotency. The description is insufficiently transparent.

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?

The description is a single concise sentence without wasted words. However, it is so brief that it omits necessary details, slightly reducing its effectiveness.

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?

The tool has 3 parameters and no output schema, yet the description doesn't mention return values, behavior of parameters, or how it relates to sibling tools. The description is incomplete for effective use.

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%, so the description must compensate for parameter meanings. It does not explain session_id (default null meaning?), clear (mutating?), or limit (what it limits). The description adds no value beyond parameter names.

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?

The description clearly states the verb 'Read' and the resource 'lifecycle events for a persistent Frida session'. It distinguishes from other 'get_events' tools by specifying the session scope, though it could clarify what lifecycle events entail.

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 given on when to use this tool versus alternatives like frida_event_get_events or frida_script_get_events. The agent is left to infer usage from the name alone.

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