Skip to main content
Glama

Stratalize Intelligence

Get Stealth Tokenize Entities

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 readOnly/destructive/openWorld annotations, the description discloses cost ($0.10 USDC per call), payment context ('one paid call'), failure semantics ('fail-closed by design'), verifiability ('cryptographically attested'), and the ephemeral-secret scope limit on determinism. These are exactly the operational traits annotations cannot express.

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?

Three tight sentences: capability first, then the consistency/account caveat, then price. Every clause carries non-redundant information and the critical constraint is front-loaded.

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?

No output schema exists, and the description compensates well by describing typed tokens plus cryptographic attestation for verification. It stops short of describing the response envelope (e.g., where tokens and attestation appear), which would fully close the 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?

With one parameter at 0% schema description coverage, the single 'text' field is only implicitly characterized as free text containing PII/entities. The description adds useful framing about what the input should contain but says nothing about size limits, accepted formats, or how entities are detected, so it only partially compensates for the coverage 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') and even names the output artifact ('deterministic typed tokens'), so an agent knows exactly what the call produces. No sibling in the catalog offers tokenization, so the lack of a named alternative is not a real ambiguity.

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 a clear selection signal: consistency holds only within a single call, and cross-session consistency or org dictionary matching 'require an account', which effectively tells the agent when this tool is insufficient. What's missing is an explicit 'use this when' framing or a pointer to the account-based path by name.

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