Skip to main content
Glama

PCI scope mapper

submit_pci_scope_mapper
Idempotent

Map a data-flow description to the systems and steps that handle cardholder data, and flag unprotected handling. At the start of a PCI scoping exercise, to sketch the in-scope systems. Do not choose this when a formal assessment or a live system scan is required. Example requests: Map the PCI scope of this payment flow. | Which systems touch cardholder data here? | Flag where card data is stored unprotected.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_pci_scope_mapper"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, and the description usefully frames the output as an advisory sketch rather than an assessment or scan. However, it never mentions that this is a priced job requiring a quote and an authorizing party, nor that invoking it submits work rather than returning a read-only answer; the pricing/authorization behavior is only inferable from the schema.

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?

Purpose is front-loaded in the first sentence, followed by usage context, a negative routing rule, and short example phrasings. Every sentence carries routing value and there is no restatement of the title or schema.

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 it covers purpose, timing, and exclusions well for a moderately complex nested-input tool. The main remaining gap is the commercial/authorization context implied by quote_id and accepted_price, which an agent would need to call this successfully in a paid flow.

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 75%, just under the high-coverage threshold, and the description adds no meaning to any of the four parameters. It does not clarify the expected shape of the flow description (free text, size limits) or the role of quote_id and accepted_price, so it neither compensates for the gap nor detracts from what the schema already states.

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 a specific verb pair and resource: map a data-flow description to the systems and steps handling cardholder data, and flag unprotected handling. That is concrete enough to separate this tool from any sibling in the list, none of which address PCI scoping.

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 states a clear usage context ('At the start of a PCI scoping exercise, to sketch the in-scope systems') and an explicit exclusion ('Do not choose this when a formal assessment or a live system scan is required'), supported by three example requests. It stops short of naming an alternative tool or service to use instead for the excluded cases, which keeps it from a 5.

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