Skip to main content
Glama

Frida Session Status

frida_session_status
Read-onlyIdempotent

Retrieve a Frida session's observed state and queued script messages to monitor runtime activity, with bounded message history and truncation reporting.

Instructions

Return observed Frida session state and queued script messages. Message history is bounded by the provider capture budget and reports truncation.

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": {
      "session_id": "00000000-0000-4000-8000-000000000001"
    },
    "name": "frida_session_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context — that message history is bounded by a provider capture budget and that truncation is reported — which is useful, but it says nothing about what 'session state' contains or what happens for an unknown/closed session.

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?

Two tight sentences, front-loaded with the primary action, with the truncation caveat following. No filler or redundancy.

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 carries the burden of describing return values; it names the two payload categories and the truncation signal but not the shape of the state object or error behavior for invalid session IDs. Adequate but leaves real gaps for a status-inspection 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 0% and the single required parameter (session_id, a UUID) is never mentioned in the description. The agent must infer from the schema alone that a session identifier is required and where to obtain it (e.g. from start_frida_session).

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: 'Return observed Frida session state and queued script messages.' This clearly separates it from the lifecycle siblings (start/close/resume_frida_session) and script siblings (load/unload_frida_script), though it never names an alternative explicitly.

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 guidance, no mention of polling cadence, and no statement of when an agent should prefer this over instrument_with_frida or the session lifecycle tools. Usage is only implied by the word 'status'.

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