ZeroTrusted-ai PII Detection Agent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| /get-detected-piisA | Analyzes text for Personally Identifiable Information (PII) using regex patterns. This function scans the input text for common PII patterns including:
Args: text (str): The text content to be analyzed for PII entities. Returns: List[Dict]: A list of detected PII entities, sorted by their position in the text. Each dictionary contains: - type (str): Type of PII detected (EMAIL, PHONE, SSN, etc.) - value (str): The actual PII string found - start (int): Starting character position in the text - end (int): Ending character position in the text Example: >>> text = "Contact john.doe@email.com or 123-456-7890" >>> get_detected_piis(text) [ { "type": "EMAIL", "value": "john.doe@email.com", "start": 8, "end": 25 }, { "type": "PHONE", "value": "123-456-7890", "start": 29, "end": 41 } ] |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear, distinct purpose focused on PII detection in text.
The single tool name follows a consistent verb_noun pattern (get_detected_piis). With only one tool, naming consistency is inherently perfect as there are no other tools to compare against.
A single tool is insufficient for a server named 'PII Detection Agent', which implies broader functionality. The scope is too narrow—typical PII detection agents might include tools for classification, redaction, or policy enforcement, not just detection.
The tool surface is severely incomplete for a PII detection agent. It only provides detection, lacking essential operations like redaction, masking, policy checking, or handling different data formats, which are core to PII management workflows.