Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_pcsc_scan

Destructive

Executes PC/SC smart-card and NFC/RFID reader scans inside an engagement workspace, passing supplied arguments directly without shell parsing.

Instructions

Run pcsc scan from the OpenCyber nfc rfid toolkit. The container executes pcsc_scan 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_pcsc_scan"
  }
}

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 the tool as destructive, open-world, and non-idempotent. The description adds useful execution context beyond that: `pcsc_scan` runs directly with argv tokens, shell parsing is never used, and paths are relative to the engagement namespace. It does not explain the nature of the destructive behavior, authentication requirements, or rate limits.

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?

The description is three sentences, front-loads the core action, and avoids redundant wording. Each sentence contributes operational detail, though the middle sentence about direct execution is somewhat dense.

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?

The description covers the execution model and working-directory convention, and an output schema exists, so return values need not be explained. However, for a destructive open-world scan with four undocumented parameters, the missing usage guidance and incomplete parameter explanations leave notable gaps.

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 schema description coverage at 0%, the description must carry parameter meaning, but it only partially does so. It clarifies that `arguments` are argv tokens and that relative paths are intended for engagement artifacts, but it does not explain `engagement_id`, `stdin`, or constraints on valid arguments.

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 states a specific verb and resource: 'Run pcsc scan from the OpenCyber nfc rfid toolkit.' It clearly identifies the underlying command as `pcsc_scan`, but it does not explicitly differentiate this from sibling scan tools such as `oc_ubertooth_scan` or `oc_bluetoothctl`.

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 description provides no explicit when-to-use guidance, no exclusions, and no named alternatives. Usage is only weakly implied by the mention of the 'nfc rfid toolkit', leaving the agent to infer whether this is the right scan tool for a given task.

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