Skip to main content
Glama

get_stealth_tokenize_entities

Read-only

Anonymize free-text PII and named entities with deterministic typed tokens in one paid call, fail-closed by design and cryptographically attested for verification. Uses a per-request ephemeral secret, so consistency is guaranteed only within the call; cross-session consistency and org dictionary matching require an account. $0.10 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: fail-closed design, cryptographic attestation, per-request ephemeral secret, within-call-only consistency, account requirements, and a $0.10 USDC charge. This is above-average disclosure for a paid transformation tool.

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?

The description is three tight sentences, front-loads the purpose, and follows with key limitations and cost. Every sentence carries operational information.

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?

There is no output schema, so the description carries the burden of explaining return behavior. It names deterministic typed tokens and cryptographic attestation but does not specify the exact response shape. Otherwise, cost, failure mode, and consistency limits are well covered.

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?

The schema has one parameter with no description coverage. The description clarifies that the input is free-text containing PII and named entities, but it does not discuss input constraints or other practical details about the text parameter. This adds some meaning but does not fully compensate for the schema gap.

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 states a specific verb and resource: anonymize free-text PII and named entities into deterministic typed tokens. This is clear enough for an agent to understand the tool's core operation without opening the schema.

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 gives clear context that this is a single paid call and warns that cross-session consistency and org dictionary matching require an account. The when-not conditions are present, but no alternative tool is named for those cases.

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