Skip to main content
Glama

ptx

Read-only

Build a permuted index from text input, displaying each word with surrounding context to create cross-reference indices.

Instructions

Build a permuted (keyword-in-context) index from input text, showing each word in its surrounding context. Read-only, no side effects. Returns JSON with the index by default; use --raw for plain output. Use to create searchable cross-reference indices. Not for sorting or deduplication — use 'sort' and 'uniq'. See also 'sort'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoWrite index rows without a JSON envelope.
onlyNoOnly include this keyword. Repeatable.
pathsNoFiles to index, or '-' for stdin. Defaults to stdin.
ignoreNoIgnore a keyword. Repeatable.
contextNoWords of left/right context.
encodingNoText encoding (default: utf-8). Use 'auto' for BOM/autodetection.utf-8
max_linesNoMaximum JSON records to emit.
ignore_caseNoCompare filters case-insensitively.
show_encodingNoInclude encoding detection metadata in JSON result.
encoding_errorsNoHow to handle encoding errors (default: replace).replace
encoding_profileNoLocale-aware encoding fallback profile for auto-detection.
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description confirms 'Read-only, no side effects.' It adds context about default JSON output and raw option, but no contradictions.

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?

Two sentences, front-loaded with purpose, no wasted words. Efficient and clear.

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?

Given 11 optional parameters and no output schema, the description covers the main output and key options. Could mention context or ignore case, but schema has full descriptions. Adequately complete for a text-processing tool.

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 description coverage is 100%, so baseline 3. The description adds minimal parameter insight beyond stating default output format. The schema already documents each parameter.

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 (Build) and resource (permuted index), and distinguishes from siblings by noting it is not for sorting or deduplication, referencing 'sort' and 'uniq'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (create searchable cross-reference indices) and when not (sorting, deduplication), with alternatives named ('sort', 'uniq') and a reference to 'sort'.

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/caseSHY/AI-CLI'

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