Skip to main content
Glama

APEX AI, LLM, Embeddings, OCR & Media

Content safety

content_safety
Read-onlyIdempotent

Fast text content-safety & moderation check across CSAM, self-harm, violence/weapons, malware, phishing scams, and severe harassment ($0.001). $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "content_safety"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to check for content-safety risk (up to 32000 chars)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare readOnly/idempotent/openWorld, so the description carries the real burden and does: exact price ($0.001 per call), accepted rails (USDC on Arc/Base/Solana, XNT on X1), and a required wallet-signing auth flow before results are returned. This is exactly the payment/auth/retry context an agent needs that structured fields do not supply.

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?

Three dense sentences, front-loaded with the capability and its category list before the payment mechanics. The $0.001 price is stated twice, which is mild redundancy, but nothing is filler.

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?

Pricing, categories, and the payment handshake are all covered, which is strong for a paid call. However, with no output schema, the description never indicates what a result contains (labels, scores, verdict shape), leaving the return value entirely opaque.

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 coverage is 100%, with both `text` (32000-char limit) and `payment` already documented in the schema. The description reinforces the `payment` flow but adds no format or validation detail beyond structured data, so the baseline 3 applies.

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?

The description names a specific verb and resource ('text content-safety & moderation check') and enumerates the harm categories it covers (CSAM, self-harm, violence/weapons, malware, phishing, harassment), which an agent can match against a need without opening the schema. It never contrasts itself with sibling tools such as bot_safety, so a 5 is not warranted.

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?

The two-step purchase protocol is spelled out precisely: call without `payment` to get terms, sign with your own wallet, call again with `payment`. That is concrete invocation guidance, but it says nothing about when to prefer this check over a sibling safety tool or what input text is appropriate.

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.