Skip to main content
Glama

renef_technique_list

Lists available technique knowledge bases and supported platforms, such as SSL pinning for Android Native, Flutter, React Native, Unity, Xamarin, and Cordova/Ionic.

Instructions

List available technique knowledge bases and their platforms (e.g. ssl_pinning: android_native, flutter, react_native, unity, xamarin, cordova_ionic).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It is clearly a read-only enumeration and the example reveals the shape of the returned mapping, but it does not state side effects, whether results are static or environment-dependent, or any access 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?

A single sentence with the core purpose front-loaded and a compact illustrative example. The parenthetical is dense but earns its place by showing the technique-to-platforms relationship.

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?

For a zero-parameter listing tool with an output schema, the description covers what is listed and roughly what comes back. The only real gap is the relationship to the sibling renef_technique, which an agent would have to infer.

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 there is nothing to disambiguate; the baseline of 4 applies. The description's example adds useful meaning about what the technique/platform values look like.

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: 'List available technique knowledge bases and their platforms', and the parenthetical example concretely shows what a technique name plus platform set looks like. It does not explicitly distinguish itself from the sibling renef_technique, so it stops short of a 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?

Usage is only implied: an agent can infer this is the discovery step that precedes selecting a technique, but the description never says when to call this instead of renef_technique or renef_module_list, nor any prerequisites.

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