Skip to main content
Glama

Check card devices for tamper signs and find the PCI questionnaire

card_skimmer_and_pos_tamper_checks
Read-onlyIdempotent

Card-skimmer and POS tamper checks for convenience stores, plus which PCI questionnaire (SAQ) your setup points to. Send devices (your own label, kind, last inspection date, and each check marked pass, fail or not_checked), and optionally a payments object with five plain answers about how cards are taken. Get back which devices need attention, which are overdue or incomplete, the suggested SAQ with the reason, the sources with dates and a signed record. Set check_sources true to also ask the PCI Council's public pages which PCI DSS version they name today. Free. No model, nothing stored. Up to 50 devices. Do NOT send card numbers, names or staff details: your own device labels only. It is a checklist and a lookup, not a security audit, a PCI assessment or legal advice; your acquirer decides which form you file.

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": {
      "devices": "<devices>"
    },
    "name": "card_skimmer_and_pos_tamper_checks"
  }
}

Input Schema

NameRequiredDescriptionDefault
devicesYes
paymentsNo
store_labelNoOptional name for the answer (not an address, not a person).
check_sourcesNoAlso fetch the PCI Council's public pages and report the PCI DSS version they name today.
inspection_interval_daysNoHow often you inspect (default 7). This is your own interval, not a PCI number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world, and the description adds substantially beyond them: the 50-device cap, 'Free. No model, nothing stored', the network fetch triggered by check_sources, the data-hygiene prohibition on card numbers/names/staff details, and the explicit non-audit disclaimer. These are exactly the behavioral facts an agent needs before calling.

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?

Purpose is front-loaded, then inputs, then outputs, then constraints and disclaimers — a sensible order for a single dense paragraph. A few sentences run long (the devices sentence), but no sentence is filler.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nested-object tool with no output schema, the description still describes the return payload (devices needing attention, overdue/incomplete, suggested SAQ with reason, dated sources, signed record), the size limit, and the liability boundary. Little an agent needs in order to call this correctly is missing.

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

Parameters4/5

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

Schema description coverage is 60%, and the description compensates well for the gaps: it explains device labels are the caller's own ('not a serial or terminal id'), that checks are pass/fail/not_checked, that payments is five plain answers, and what check_sources actually does. Only inspection_interval_days, store_label and the specific check names are left to the schema, which documents those adequately.

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?

The description names the specific resource and action: card-skimmer and POS tamper checks for stores, plus the PCI SAQ the setup points to. It also bounds the scope with 'It is a checklist and a lookup' — an agent can tell what class of tool this is without opening the schema.

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?

Usage context is explicit ('for convenience stores'), the optional branch is spelled out ('set check_sources true to also ask the PCI Council's public pages'), and exclusions are stated ('not a security audit, a PCI assessment or legal advice; your acquirer decides which form you file'). It does not name an alternative tool to use instead, but no obvious competing sibling requires routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources