Skip to main content
Glama

Map an NFC card to a game

mister_map_nfc_card
Idempotent

Associates a physical NFC card UID with a Zaparoo game without writing to the card, so read-only cards, amiibo, and arcade tokens can launch the mapped game.

Instructions

<use_case> Associate a physical card UID with a game in Zaparoo without writing to the card. </use_case> <important_notes>

  • Suitable for read-only cards, amiibo, or arcade tokens.

  • Uses last scanned UID if uid parameter is omitted. </important_notes>

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": {
      "game": "<game>"
    },
    "name": "mister_map_nfc_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidNoThe card's UID. Omit to use the card scanned on that MiSTer in the last 2 minutes.
gameYesA game ref from mister_search_games or mister_play_history, e.g. 'Family Room/4812'.

Output Schema

NameRequiredDescriptionDefault
hostYes
detailYes
outcomeYes
warningsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-destructive, idempotent, non-read-only behavior, so the description need not repeat that. It adds value beyond annotations by clarifying that the physical card itself is left unmodified and that the mapping still occurs server-side, which annotations cannot express. It omits what happens if no card was scanned recently or whether an existing mapping for that game is replaced.

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 tagged sections with the use case front-loaded and no filler prose. The uid-omission note duplicates the parameter description, which is minor waste, but overall the structure is easy to scan.

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 only two parameters, full schema coverage, and an output schema available, the description covers purpose, suitable card types, and default UID behavior adequately. The remaining unknown — failure mode when no recent scan exists and overwrite semantics for an already-mapped game — is a modest gap for a non-destructive, idempotent operation.

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 coverage is 100% and the schema itself already documents both uid and game, including the 'omit to use the last scanned card' default and the game-ref format. The description's note on the uid default restates schema information rather than adding syntax or format detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose5/5

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

States a specific verb and resource: associate a physical card UID with a game in Zaparoo. The qualifier 'without writing to the card' implicitly separates it from the sibling write tool, so an agent can distinguish the mapping operation from the card-writing operation.

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?

Gives concrete usage conditions ('suitable for read-only cards, amiibo, or arcade tokens'), which tells the agent what kind of card warrants this tool rather than a write. It stops short of naming the alternative tool or stating exclusions explicitly, so the contrast with writing to a card is implied rather than spelled out.

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