Skip to main content
Glama

Resume Redaction

redact_resume
Read-onlyIdempotent

Redacts personally identifiable information from candidate profiles to support anonymized review, bias-aware screening, compliance workflows, and audit logs. Configurable redaction scope. Idempotent.

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

Input Schema

NameRequiredDescriptionDefault
filenameNoOptional for resume_text (default 'inline_resume.txt'). Required for resume_base64 and must include the original file extension.
jsondataNoPre-parsed resume JSON string (skips re-parsing when provided).
masktypeNoHow masked fields render — 'x-value' (default, replaces with XXXXXXXXX) or 'null-value' (removes the field entirely).x-value
maskfieldsNoFields to redact/hide — JSON array or comma-separated string, e.g. ["Name","Email","PhoneNumber"] or "Name, Email, Phone". When omitted, the server's default redaction set is applied.
resume_textNoComplete, verbatim plain-text of the resume/CV — every line as in the original. Do NOT summarise or base64-encode; pass raw text.
abbreviationNoSet True to enable abbreviation mode globally.
abbfieldcolorNoHex colour for abbreviation highlights.
resume_base64NoRaw Base64-encoded resume file content (PDF, DOC, DOCX, RTF, TXT). Provide the original filename. Use either resume_text or resume_base64, not both. Do not include a data URI prefix.
highlightcolorNoHex colour to highlight redacted regions (e.g. '#FFFF00').
abbreviationfieldsNoFields to abbreviate rather than mask — JSON array or comma-separated string (e.g. 'Name' -> 'J.D.').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / filename / description
      Previous value: -"Optional original filename (e.g. 'resume.pdf'). Defaults to 'inline_resume.txt'; '.txt' is appended if missing."New value: +"Optional for resume_text (default 'inline_resume.txt'). Required for resume_base64 and must include the original file extension."
    • addedInput schema / properties / resume_base64
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Raw Base64-encoded resume file content (PDF, DOC, DOCX, RTF, TXT). Provide the original filename. Use either resume_text or resume_base64, not both. Do not include a data URI prefix.",
      +  "title": "Resume Base64"
      +}
    • addedInput schema / properties / resume_text / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / resume_text / default
      Previous value: -""New value: +null
    • changedInput schema / properties / resume_text / description
      Previous value: -"Required. Complete, verbatim plain-text of the resume/CV — every line as in the original. Do NOT summarise or base64-encode; pass raw text."New value: +"Complete, verbatim plain-text of the resume/CV — every line as in the original. Do NOT summarise or base64-encode; pass raw text."
    • removedInput schema / properties / resume_text / type
      Removed value: -"string"
  2. Changed2 schema fields changed
    • removedInput schema / properties / subuserid
      Removed value: -{
      -  "default": "",
      -  "description": "Sub-user identifier for multi-tenant isolation.",
      -  "title": "Subuserid",
      -  "type": "string"
      -}
    • removedInput schema / properties / userkey
      Removed value: -{
      -  "default": "",
      -  "description": "RChilli API userkey. Leave blank to use the authenticated session key.",
      -  "title": "Userkey",
      -  "type": "string"
      -}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so "Idempotent" in the description is a restatement that earns no credit. The only genuine addition is "Configurable redaction scope," which is left unexplored; with no output schema, the description should say what comes back (redacted text vs. file vs. masked-field report) and what happens when neither resume_text nor resume_base64 is supplied.

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?

Two sentences, front-loaded with the action and followed by the qualifier, with no wasted framing. The trailing four-item use-case list is the one portion that could be trimmed or converted into real routing guidance.

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

Completeness3/5

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

For a 10-parameter tool with zero required fields, four mutually exclusive input modes and no output schema, the description is thin on the two things an agent most needs: which input mode to choose and what the response contains. The schema covers the parameters well, but the return contract is left entirely undefined.

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% and the schema is unusually explicit about mutually exclusive inputs, masktype rendering and field lists, so the schema carries the load. The description adds only the vague phrase "Configurable redaction scope," which does not clarify maskfields vs. abbreviationfields or the interaction between them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb+resource combination ("redacts personally identifiable information from candidate profiles") that is clearly distinct from sibling tools like extract_resume_data or detect_bias. It stops short of naming which sibling to use when the goal is analysis rather than redaction, so differentiation is implied rather than explicit.

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 four listed scenarios (anonymized review, bias-aware screening, compliance workflows, audit logs) sketch the context in which to reach for this tool, but they read as marketing use cases rather than routing rules. There is no guidance on when NOT to use it, no mention of preceding steps such as extract_resume_data, and no tie-breaking against siblings like detect_resume_suspicion.

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