Skip to main content
Glama

Civify

by cv.civify.mcp
OverviewDiscussionsAdmin

Mask Personally Identifiable Information

civify_mask_pii
Idempotent

Sanitize and redact sensitive PII (email, phone, physical address) from a CV document, exporting an anonymized PDF.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNoOptional API key override.
file_base64NoBase64 encoded resume file (PDF, DOCX). Recommended for remote/cloud MCP servers.
output_pathNoOptional destination path on the server to save the masked PDF.
server_file_pathNoLocal file path on the MCP server machine. For local CLI/stdio usage only. In ChatGPT or Claude, pass 'file_base64' instead.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoFilesystem path to saved masked PDF
statusYesRedaction status (SUCCESS)
messageYesDetails on the exported sanitized document
pdf_base64NoBase64 encoded masked PDF if saved to memory

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / file_base64 / description
      Previous value: -"Base64 encoded resume file."New value: +"Base64 encoded resume file (PDF, DOCX). Recommended for remote/cloud MCP servers."
    • removedInput schema / properties / file_path
      Removed value: -{
-  "description": "Path to resume file to redact.",
-  "type": "string"
-}
    • changedInput schema / properties / output_path / description
      Previous value: -"Optional destination path to save the masked PDF."New value: +"Optional destination path on the server to save the masked PDF."
    • addedInput schema / properties / server_file_path
      Added value: +{
+  "description": "Local file path on the MCP server machine. For local CLI/stdio usage only. In ChatGPT or Claude, pass 'file_base64' instead.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds the fact that it exports a new PDF, but does not disclose whether the original file is modified or any side effects. It does not contradict annotations.

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?

A single sentence that is front-loaded with the core action and output, with no wasted words. It is appropriately concise.

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?

Given the tool's simplicity, the presence of an output schema, and annotations covering safety, the description is adequate. It clearly defines the input type (CV) and output format (PDF), though it could mention authentication or file handling nuances.

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 100%, so all four parameters are already documented. The description does not add meaningful semantics beyond what the schema provides, such as clarifying the api_key requirement or output_path behavior.

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 clearly states the verb (sanitize/redact), resource (CV document), and output (anonymized PDF), distinguishing it from sibling tools like parse or tailor.

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 description implies usage (sanitize PII) but does not explicitly state when to use this tool versus alternatives or any exclusions. It lacks guidance on prerequisites like authentication or when not to use it.

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

All Civify toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources