Skip to main content
Glama

Write a game to an NFC card

mister_write_nfc_card
Destructive

Write game launch metadata to an NFC card on a compatible writer, overwriting existing tag data so scanning the card launches the chosen game.

Instructions

<use_case> Write game launch metadata to an NFC card on a compatible writer. </use_case> <important_notes>

  • DESTRUCTIVE: Overwrites existing payload on the NFC tag.

  • Prompts user to place card on reader; waits up to 60s. </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_write_nfc_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYesA game ref from mister_search_games or mister_play_history, e.g. 'Family Room/4812'.
readerNoReader id from mister_list_nfc, when there's more than one.

Output Schema

NameRequiredDescriptionDefault
hostYes
detailYes
outcomeYes
warningsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotent, but the description goes further: it states the existing tag payload is overwritten and that the call blocks while prompting the user to place a card, waiting up to 60s. That interaction and timeout detail is real value an annotation cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two labeled sections, each one sentence, front-loading the use case and then the destructive/timeout warnings. No filler or repetition of the tool title.

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?

An output schema exists, so return values need not be explained, and the description covers the two things an agent most needs to know before calling: it is destructive and it blocks for up to a minute. Only the distinction from the sibling NFC mapping tool is left implicit.

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%, with the game ref format and reader-selection guidance fully documented in the schema. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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: writes game launch metadata to an NFC card on a compatible writer. It clearly separates this from read-oriented siblings like mister_list_nfc, but does not explicitly contrast with mister_map_nfc_card, which an agent might reasonably confuse it with.

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

Usage Guidelines3/5

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

The use case block implies when to use it (writing a game's launch metadata to a tag), but gives no explicit alternatives or exclusions. The 'compatible writer' and 'reader when more than one' conditions live in the schema rather than the description, so routing guidance is only implied.

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