Skip to main content
Glama

Load Frida Script

load_frida_script
Destructive

Loads caller-supplied JavaScript into a Frida session to inspect or modify target memory and behavior, returning messages and script errors inline as Evidence.

Instructions

Load caller-supplied JavaScript into a Frida session. Scripts can read or change target memory and behavior and can access the target process's capabilities. Messages and script errors are returned inline as Evidence; source content is not persisted.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source": "send(Process.id);",
      "session_id": "00000000-0000-4000-8000-000000000001",
      "source_kind": "inline"
    },
    "name": "load_frida_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoLocal filesystem path used by this operation.
sourceNo
session_idYes
source_kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and openWorldHint=true, so the risk profile is known. The description usefully adds that scripts can read or modify target memory and behavior, that messages and errors return inline as Evidence, and that source content is not persisted – genuine context beyond the annotations, though it says nothing about replacement of previously loaded scripts or permission requirements.

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?

Three tight sentences, front-loaded with the action and its consequence, with no padding. Slightly dense in the middle sentence but every clause carries information an agent needs.

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?

With no output schema, the description does a decent job explaining that results arrive as inline Evidence, but it omits the parameter coupling (path vs source via source_kind) and session prerequisites, which matter for a 4-parameter destructive tool.

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 only 25%: only 'path' carries a description, while session_id, source_kind and source are undocumented. The description does not compensate – it never explains the inline/file switch, that 'path' is used with source_kind=file, or the relationship between source and path.

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?

States a specific verb and resource: loading caller-supplied JavaScript into a Frida session. It is clearly distinct in intent from unload_frida_script, but it never explicitly contrasts itself with siblings like instrument_with_frida, leaving the agent to infer the division of labor.

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?

There is no when-to-use/when-not guidance and no mention of prerequisites such as an active session or of alternatives like unload_frida_script or instrument_with_frida. The agent must infer the lifecycle position of this tool from names 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