Skip to main content
Glama

create_list_from_shell

Generate lists by executing shell commands and parsing their newline-delimited output for batch processing operations.

Instructions

Creates a list by running a shell command and parsing its newline-delimited output.

WHEN TO USE:

  • When you need to create a list from command output (e.g., find, ls, grep, git ls-files)

  • When the list of items to process is determined by a shell command

  • As an alternative to manually specifying items in create_list

EXAMPLES:

  • "find src -name '*.ts'" to get all TypeScript files

  • "git ls-files '*.tsx'" to get all tracked TSX files

  • "ls *.json" to get all JSON files in current directory

  • "grep -l 'TODO' src/**/*.ts" to get files containing TODO

WORKFLOW:

  1. Call create_list_from_shell with your command

  2. The command's stdout is split by newlines to create list items

  3. Empty lines are filtered out

  4. Use the returned list_id with run_shell_across_list or run_agent_across_list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesShell command to run. Its stdout will be split by newlines to create list items. Example: 'find src -name "*.ts"' or 'git ls-files'
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's behavior: it runs a shell command, splits stdout by newlines to create list items, filters out empty lines, and returns a list_id for use with other tools. However, it lacks details on error handling, timeouts, or security implications (e.g., command injection risks), which would be needed for a perfect score.

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 well-structured with clear sections (description, WHEN TO USE, EXAMPLES, WORKFLOW), each sentence adds value, and it avoids redundancy. It's appropriately sized for a tool with one parameter and no annotations, making it efficient and easy to parse.

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 the tool's moderate complexity (one parameter, no annotations, no output schema), the description is largely complete. It covers purpose, usage, examples, and workflow. However, it doesn't specify the return value format (e.g., what list_id is or how to use it), which is a minor gap since there's no output schema to compensate.

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?

The schema description coverage is 100%, so the baseline is 3. The description adds value by explaining that the command's stdout is split by newlines to create list items, which clarifies the parameter's purpose beyond the schema's example. However, it doesn't provide additional syntax or format details, keeping it slightly above baseline.

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 clearly states the tool's purpose: 'Creates a list by running a shell command and parsing its newline-delimited output.' It specifies the verb ('creates'), resource ('list'), and mechanism ('shell command'), distinguishing it from sibling tools like create_list (manual specification) and run_shell_across_list (operates on existing lists).

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?

The 'WHEN TO USE' section explicitly lists three scenarios for usage, including 'As an alternative to manually specifying items in create_list,' which directly compares it to a sibling tool. This provides clear guidance on when to choose this tool over alternatives, fulfilling the highest scoring criteria.

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/mathematic-inc/par5-mcp'

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