Skip to main content
Glama
altrsoftware

ALTR MCP Server

Official
by altrsoftware

critical_tokenize

Tokenize plaintext strings into critical tokens that can be later detokenized. Supports deterministic tokenization for consistent results.

Instructions

Tokenize plaintext values using ALTR critical tokenization.

Replaces plaintext strings with critical tokens (format: token_XXXX..., 64+ chars). Tokens can be detokenized later. Deterministic tokenization produces the same token for the same input value.

Maximum 1024 values per call. Each value must be under 128 UTF-8 code units.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valuesYesDict mapping user-defined keys to plaintext strings to tokenize (e.g. {"ssn": "123-45-6789", "email": "user@example.com"}).
deterministicNoIf True, the same plaintext always produces the same token. Default False (random token each time).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Discloses token format (token_XXXX..., 64+ chars), detokenization ability, deterministic vs random option, and size limits. No contradictions with annotations (none provided).

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?

Well-structured with clear sections, front-loading the main action. Each sentence adds value, no redundancy. Concise yet complete.

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

Completeness5/5

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

Given no annotations but high schema coverage and presence of output schema, the description sufficiently covers behavior, constraints, and parameters. All necessary context for correct invocation is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers both parameters (values, deterministic) with descriptions. Description adds context: token format, deterministic behavior effect, and 128 code units limit per value, enhancing understanding beyond schema.

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?

Description clearly states it tokenizes plaintext using ALTR critical tokenization, with format and behavioral details. It distinguishes from siblings like vault_tokenize by specifying 'critical tokenization', though not explicitly contrasting.

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?

Provides constraints (max 1024 values, 128 UTF-8 code units per value) and mentions detokenization capability. Does not explicitly state when to use this tool vs alternatives like vault_tokenize or critical_detokenize.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/altrsoftware/altr-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server