Skip to main content
Glama

Fairquery Agent Trust & Data Safety

Fortress Shield: list PII/secret detectors and pricing (free)

pii_list_detectors
Read-onlyIdempotent

WHAT: Fortress Shield (agent I/O PII protection). Catalog of every PII and secret entity type, which ones the free tools run on this Worker (pii_scan_text / pii_redact_text) vs only in the paid Actor (NER names/locations, and fetching remote PDF/document URLs; http(s) URLs in text are detected locally; STREET_ADDRESS patterns run locally with detectAddresses), redaction styles, sealed-map support, and the price of every paid tool in this server. WHEN: Before pii_scan_text / pii_redact_text to pick entityTypes, or to explain coverage and costs to a user. WHEN NOT: To actually scan text (pii_scan_text) or redact it (pii_redact_text). COST: Free; no token. RETURNS: One catalog object; local:true marks the detectors the free tools run (see PARAMETERS). features.sealed_map.available says whether this deployment can seal placeholder maps. BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs, results, or an Apify token. No further network call; the catalog is compiled into this Worker, instant (<10 ms). No rate limits. PARAMETERS: None: call with an empty object {}; the catalog is always complete and cannot be filtered. Its output feeds other tools' parameters: copy detector "type" values verbatim into entityTypes of pii_scan_text / pii_redact_text (only rows with local:true can match there) or pii_guard_documents (all rows, incl. PERSON / LOCATION / STREET_ADDRESS); redaction_styles keys are the allowed redactionStyle values. EXAMPLE: {} -> {"detectors":[{"type":"AWS_ACCESS_KEY","category":"secret","local":true},...]}

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
featuresNo
detectorsYes
paid_pricingYes
redaction_stylesYes
receipt_verificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / receipt_verification
      Added value: +{
      +  "additionalProperties": {},
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / features
      Added value: +{
      +  "additionalProperties": {},
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/no-open-world, yet the description still adds execution locus (Fairquery-hosted Cloudflare Worker, not the caller's machine), data-handling posture (designed not to store inputs, results, or a token), no downstream network call, sub-10ms latency, and no rate limits. That is behavioral context beyond what the annotations convey, and it is consistent with them.

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?

Labeled sections (WHAT/WHEN/WHEN NOT/COST/RETURNS/BEHAVIOR/PARAMETERS/EXAMPLE) make it skimmable and front-loaded. It is long, and the local:true semantics are restated in both RETURNS and PARAMETERS, which is mild redundancy for a tool whose actual behavior is trivially simple.

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?

Covers cost, determinism, network/execution environment, and consumption of the result by sibling tools; even though an output schema exists and would excuse skipping return values, the description still gives an inline example. Nothing an agent needs in order to call it correctly or use its output is missing.

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

Parameters5/5

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

With zero parameters the baseline is 4, but the description earns the extra point by documenting the calling convention (empty object {}, catalog cannot be filtered) and, more importantly, how the output maps onto other tools' parameters — copy detector "type" verbatim into entityTypes, only rows with local:true can match in the free scanners, all rows for pii_guard_documents, and redaction_styles keys are the allowed redactionStyle values.

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?

"Catalog of every PII and secret entity type" plus what the free tools run locally vs. only in the paid Actor is a specific resource statement, and it explicitly names the sibling tools (pii_scan_text / pii_redact_text) it is not. It even enumerates the catalog's sections: detector types, redaction styles, sealed-map support, and pricing.

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

Usage Guidelines5/5

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

Dedicated WHEN ("before pii_scan_text / pii_redact_text to pick entityTypes, or to explain coverage and costs") and WHEN NOT ("to actually scan text or redact it") clauses route the agent unambiguously. The named alternatives are exactly the correct siblings.

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