Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_nfc_list

Destructive

Lists NFC devices and tags visible to PC/SC or libnfc readers, helping identify available contactless targets within an engagement workspace.

Instructions

List NFC devices and tags visible to a PC/SC or libnfc reader. 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_list"
  }
}

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

B3/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 readOnlyHint=false, so the safety profile is carried structurally. The description adds context the annotations do not: the tool executes inside the selected engagement namespace and artifact paths should be relative, which is real operational information. It says nothing about hardware/reader requirements, whether RF is emitted, or that the 'list' framing sits alongside a destructive annotation, leaving that tension unexplained.

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?

Two short sentences with no filler; the purpose is front-loaded and the operational note follows. It is efficient, though the second sentence is terse enough that its meaning is somewhat compressed.

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-shape explanation is unnecessary, and annotations cover the safety profile. What is missing is the meaning of the required free-form 'arguments' passthrough and any hardware prerequisite, which an agent needs to call this without trial and error.

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% across four parameters, so the description must compensate and largely does not. It maps loosely to engagement_id (namespace) and working_directory (relative paths), but the required 'arguments' array of raw CLI strings and the optional 'stdin' are never explained, which is the biggest omission for an agent trying to invoke this correctly.

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?

The description names a specific verb and resource ('List NFC devices and tags') and even names the underlying stacks (PC/SC or libnfc reader), which tells an agent exactly what class of operation this is. It stops short of differentiating itself from NFC siblings such as oc_nfc_poll or oc_nfc_mfclassic, so an agent cannot tell from this text alone which NFC entry point to choose.

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 explicit when-to-use or when-not-to-use guidance and no statement of prerequisites beyond the implicit hint that a reader must be present. The only routing information is 'use relative paths for engagement artifacts', which concerns pathing rather than tool selection.

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