Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_nfc_poll

Destructive

Polls for a single NFC tag and reports its UID and technology, using the selected engagement namespace and relative artifact paths.

Instructions

Poll for one NFC tag and report its UID and technology. 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_poll"
  }
}

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.6/5.0
Behavior2/5

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

Annotations declare destructiveHint=true, readOnlyHint=false, openWorldHint=true and non-idempotent, yet the description frames the operation as a pure read that 'reports' a UID — that tension is never resolved, so an agent cannot tell what is actually put at risk. The only added behavioral context is namespace scoping and relative-path usage; nothing about timeouts, reader contention, or what happens if no tag is present.

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 the core action front-loaded and no filler. The second sentence is arguably operational boilerplate but it is at least compact and non-redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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, but for a four-parameter, destructive-flagged wrapper tool the description leaves too much open: the arguments array is unexplained, and the destructive annotation is neither justified nor warned about.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for four parameters, so the description carries the full burden, and it explains none of them — engagement_id, arguments, stdin and working_directory are all undocumented. The phrase 'use relative paths for engagement artifacts' is the only hint, and it does not clearly map to any single parameter.

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 ('Poll for one NFC tag') and even names the returned data ('UID and technology'), which lets an agent distinguish it from a listing-style sibling such as oc_nfc_list. It stops short of explicitly contrasting itself with those siblings, so it is clear but not fully differentiated.

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 second sentence gives operational context (engagement namespace, relative artifact paths) but never says when to choose this tool over alternatives like oc_nfc_list or the MIFARE-specific tool, nor any precondition such as a connected reader. There is no when-not guidance at all.

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