Literal Enumeration Token Check
Check exact membership in a caller-provided literal token enumeration; no case folding, aliases or authoritative vocabulary.
Description
Check exact membership in a caller-provided literal token enumeration; no case folding, aliases or authoritative vocabulary.
An enumeration membership check compares a token with a declared allowed vocabulary.
When to use this tool
Check exact membership in a caller-provided literal token enumeration; no case folding, aliases or authoritative vocabulary.
- Prepare the supplied token, allowed fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter token, allowed. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.member. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require allowed to contain unique strings and return whether it contains token by exact equality.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| token | token. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| allowed | allowed. | List of strings; at most 128 entries |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.member | Membership flag for the specific set and boundary convention above. |
{
"input": {
"token": "A",
"allowed": [
"A",
"B"
]
},
"output": {
"result": {
"member": true
}
}
}Limitations and assumptions
- No trimming, alias expansion or case normalization is performed. A false membership result is distinct from malformed input.
- All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
- JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.
Alternative or Complementary methods
Use a parser for the actual target format when the task requires CSV, shell, URL, calendar or filesystem semantics. These tools implement the specific small grammars stated here, without adding those surrounding conventions.
References
Similar or alternative tools
- Literal Enumeration Alias Resolver
Resolve caller-defined enumeration aliases with cycle/path evidence and check the terminal against an explicit allowed bank.
- Balanced Parenthesis Token Splitter
Split a literal delimiter only outside balanced parentheses; parentheses are retained, quotes and escapes have no special meaning.