Synthex Forge — x402 Paid Agent Services

Redact Pii

redact_pii

Read-onlyIdempotent

Utils Pii Redact. use it rather than clean_json_schema for pii, not json schema; an object with 11 fields including hidden, index. $0.25 USDC.

Input Schema

Name	Required	Description	Default
`text`	No	The source text the operation operates on.
`redact_names`	No	The redact names this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`kind`	No	The `kind` field of the response.
`note`	No	A note on how the answer was produced.
`type`	No	The `type` field of the response.
`index`	No	The `index` field of the response.
`hidden`	No	The `hidden` field of the response.
`utility`	No	The `utility` field of the response.
`redacted`	No	The `redacted` field of the response.
`redactions`	No	The `redactions` field of the response.
`input_preview`	No	The `input_preview` field of the response.
`utility_result`	No	The `utility_result` field of the response.
`redaction_count`	No	The `redaction_count` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 31, 2026

addedOutput schema / properties / hidden

Added value: +{
+  "description": "The `hidden` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / index

Added value: +{
+  "description": "The `index` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / input_preview

Added value: +{
+  "description": "The `input_preview` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / kind

Added value: +{
+  "description": "The `kind` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "A note on how the answer was produced.",
+  "type": "string"
+}

addedOutput schema / properties / redacted

Added value: +{
+  "description": "The `redacted` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / redaction_count

Added value: +{
+  "description": "The `redaction_count` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / redactions

Added value: +{
+  "description": "The `redactions` field of the response.",
+  "type": "object"
+}

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / type

Added value: +{
+  "description": "The `type` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / utility

Added value: +{
+  "description": "The `utility` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / utility_result

Added value: +{
+  "description": "The `utility_result` field of the response.",
+  "type": "object"
+}

AddedOct 31, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely useful non-schema context in the "$0.25 USDC" per-call cost, but the "an object with 11 fields including hidden, index" fragment is redundant with the existing output schema and is too cryptic to be actionable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but two of the three clauses are garbled machine-generated fragments ("Utils Pii Redact", "an object with 11 fields including hidden, index") that read as template noise rather than front-loaded information. The routing rule and price are buried mid-sentence.

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?

Cost and the key sibling distinction are covered, and an output schema exists so return values need not be explained. However, for a paid transformation tool the description never says what redaction actually does to the text or whether redact_names toggles name-specific behavior, leaving a meaningful gap.

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% across both parameters (text, redact_names), so the schema already carries parameter meaning. The description adds nothing about them, which is acceptable at full coverage — baseline 3.

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

Purpose3/5

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

"Utils Pii Redact" essentially restates the tool name and category; the only substantive purpose content is the clause scoping it to PII rather than JSON schema. An agent can infer it redacts PII, but the description never explains what redaction means here (masking, removal, hashing) or what the operation returns.

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 explicitly names the alternative — "use it rather than `clean_json_schema` for pii, not json schema" — giving a concrete selection rule against a real sibling. It lacks any when-not conditions or prerequisites beyond that single comparison, so it stops short of a 5.

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

All Synthex Forge — x402 Paid Agent Services tools Inspect

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.