Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_nfc_mfclassic

Destructive

Run MIFARE Classic RFID operations via nfc-mfclassic in an engagement workspace, passing arguments directly without shell parsing and using relative paths for artifacts.

Instructions

Run nfc mfclassic from the OpenCyber nfc rfid toolkit. The container executes nfc-mfclassic directly with the supplied argv tokens; shell parsing is never used. Runs from the selected engagement namespace; use relative paths for engagement artifacts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "engagement_id": "<engagement_id>",
      "arguments": "<arguments>"
    },
    "name": "oc_nfc_mfclassic"
  }
}

Input Schema

NameRequiredDescriptionDefault
stdinNo
argumentsYes
engagement_idYes
working_directoryNo.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and non-idempotent, so the safety profile is known. The description adds genuinely useful execution semantics beyond that: argv tokens are passed directly and shell parsing is never used, which tells an agent not to quote or chain commands. It stops short of saying what destruction means here (overwriting tag contents, hardware/reader dependency), which matters for a destructive hardware operation.

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 short sentences, front-loaded with the action and followed by the execution model and path convention. No filler, though the middle sentence about shell parsing could be tightened.

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. For a destructive, open-world CLI wrapper with entirely undocumented parameters and no indication of hardware prerequisites or what the wrapped command does, the description is adequate on execution mechanics but thin on operational context.

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?

With 0% schema description coverage across four parameters, the description carries the full burden. It obliquely clarifies 'arguments' as argv tokens and hints that working_directory should be relative to the engagement, but it says nothing about engagement_id or stdin, leaving half the parameters undocumented in both schema and prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact binary it wraps ('nfc-mfclassic') and the toolkit it comes from, so an agent knows this is a CLI passthrough. However, it never says what the underlying tool actually does (read/write Mifare Classic tags), and it gives no contrast with siblings like oc_nfc_list or oc_nfc_poll, so an agent cannot tell from the text alone when this is the right NFC tool.

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?

The only routing-adjacent guidance is namespace/path advice ('Runs from the selected engagement namespace; use relative paths for engagement artifacts'), which is about invocation mechanics, not tool selection. There is no when-to-use, when-not-to-use, or named alternative, despite several NFC siblings existing.

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