Skip to main content
Glama

List NFC readers and cards

mister_list_nfc
Read-only

Lists connected NFC readers, card-to-game mappings, and the last scanned card UID so you can confirm write support before mapping cards.

Instructions

<use_case> List connected NFC readers, card-to-game mappings, and the last scanned card UID. </use_case> <important_notes>

  • Use this to check whether a reader supports write operations (can_write=True).

  • Returns the last scanned card UID for mister_map_nfc_card workflows. </important_notes>

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": "mister_list_nfc"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoMiSTer name from mister_get_status. Omit when the call already says which (a ref does).

Output Schema

NameRequiredDescriptionDefault
hostYes
readersYes
mappingsYes
last_cardYes
last_card_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that the result includes a can_write capability flag and the last scanned UID, which is useful behavioral framing. It does not discuss freshness, caching, or what happens when no reader is connected, and the output schema already carries the return shape.

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 use_case/important_notes structure is front-loaded and compact, with no filler. The second note slightly restates the use_case's mention of the last scanned UID, a small redundancy.

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?

With an output schema present, the description need not explain return values, and annotations cover the read-only profile. Purpose, scope, and the main consuming workflow are all stated. Only edge-case behavior (no readers connected, stale UID) is missing.

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

Parameters3/5

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

Schema description coverage is 100% and the single host parameter is documented in the schema, including its default and its mister_get_status origin. The description adds nothing about host resolution, so the baseline of 3 is appropriate.

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 and enumerates exactly what is returned: connected readers, card-to-game mappings, and the last scanned UID. It is clearly distinguishable from a mutating sibling like mister_map_nfc_card, though it does not explicitly contrast itself with any alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives two concrete when-to-use signals: checking whether a reader supports writes (can_write=True) and retrieving the last scanned UID for mister_map_nfc_card workflows. There are no explicit exclusions or when-not conditions, which keeps it short of a 5.

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