Skip to main content
Glama

renef_framework_detect

Detects an Android app's framework—Flutter, React Native, Unity, Xamarin, or Cordova/Ionic—by checking for characteristic libraries; requires an active session.

Instructions

Detect the app framework (Flutter, React Native, Unity, Xamarin, Cordova/Ionic) by checking for its characteristic libraries. Needs a 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": "renef_framework_detect"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden itself; it discloses the prerequisite (an active session) and the inspection method ('checking for its characteristic libraries'), which implies a read-only probe. It does not state whether detection is heuristic/best-effort, what happens when no framework matches, or whether it causes any side effects on the target.

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 sentences, both front-loaded with the useful information: what is detected and the enumerated targets first, the session prerequisite last. No redundant restatement of the name.

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?

An output schema exists and there are no parameters, so return values need not be explained; the prerequisite and method are covered. The only omission is the reliability/none-found behavior of the detection, which is a minor gap for a zero-parameter tool.

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?

The tool takes zero parameters, so the baseline of 4 applies; the description correctly implies that everything is derived from the current session state rather than from inputs.

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 ('Detect') and resource ('the app framework') and enumerates exactly what can be returned (Flutter, React Native, Unity, Xamarin, Cordova/Ionic), which no sibling tool does. It does not explicitly contrast itself with similarly-scoped siblings such as renef_attach or renef_list_apps, so it stops short of 5.

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

Usage Guidelines3/5

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

The phrase 'Needs a session' gives a concrete prerequisite, which tells an agent this must follow attach/spawn. However, there is no explicit statement of when to prefer this over probing frameworks by hand or in combination with renef_module_list, and no when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.