Skip to main content
Glama

renef_technique

Returns an assembled technique guide for a given platform and category, such as bypassing SSL pinning on Flutter, React Native, Unity, or Xamarin apps.

Instructions

Return the assembled technique guide for a platform, e.g. renef_technique("ssl_pinning", "flutter") or platform="react_native"/"unity"/"xamarin".

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_technique"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNossl_pinning
platformNoandroid

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden; "Return" implies a read-only operation but that is never stated outright. It does add some behavioral context by naming acceptable platform values and implying the output is a pre-assembled document, but it says nothing about failure modes, whether unknown categories error or return empty, or how the defaults are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the purpose, which is good. However, the example is written as unnamed positional arguments, forcing the agent to infer which value maps to which parameter, and the alternation of example style with a keyword-style argument is slightly muddled.

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?

An output schema exists, so return values need not be explained, and two parameters is low complexity. Still, with zero schema description coverage, the description leaves the category value space and the default behavior undocumented, which is a meaningful gap for a tool whose whole value depends on picking the right category.

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 0% — the schema offers only bare "Category"/"Platform" titles with defaults — so the description must compensate. The worked example usefully reveals positional order (category first, then platform) and enumerates flutter/react_native/unity/xamarin, but it never enumerates valid categories beyond ssl_pinning and never mentions the schema defaults (ssl_pinning/android).

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?

It names a specific verb and resource ("Return the assembled technique guide") and scopes it to a platform, so the agent can tell it produces a composed guide rather than a listing. The word "assembled" hints at the distinction from renef_technique_list, but that sibling is never named, so the separation is inferred rather than stated.

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?

Usage is only implied: the example calls show you invoke it with a category and platform to get a guide. There is no explicit when-to-use guidance, no statement of when renef_technique_list would be the better choice, and no note on prerequisites or error behavior for unknown categories.

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