Skip to main content
Glama
OnStartups

Agent.ai MCP Server

by OnStartups

get_user_list

Collect a comma-separated or newline-separated list of items from user input, using a configurable delimiter.

Instructions

Capture a list of items from a textarea and split on a delimiter or newline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
input_descriptionYesWrite a clear prompt to guide users on what information is required. For example, 'Please enter your email address' or 'Select your preferred contact method.'
delimiterNoThis is the character that separates the list items. For example, use a comma (,) for 'item1,item2,item3'. Leave blank to split on newlines.
requiredNoMark this checkbox if this input is mandatory. For example, enable it if a response is essential to proceed in the workflow.
input_nameYesAssign a unique variable name for the input value, such as 'user_email' or 'preferred_contact', which you can reference later in the workflow.user_input
Behavior3/5

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

With no annotations provided, the description bears full responsibility. It conveys the basic action (capture and split) but omits details on the interactive nature (presumably involves displaying a textarea to the user), output format, or potential side effects. The description is adequate but shallow.

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 a single sentence that efficiently captures the core functionality. No superfluous information is present.

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

Completeness3/5

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

For a tool with 4 parameters and no output schema, the description is minimal. It does not explain what the tool returns or how parameters interact, though the schema fills some gaps. The description is adequate for a simple input capture but lacks completeness for an agent to fully understand the tool's behavior.

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 the schema already documents all parameters. The description adds no extra meaning or context for the parameters beyond what the schema provides.

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?

The description clearly states the tool captures a list from a textarea and splits it by delimiter or newline. It distinguishes its purpose from siblings by focusing on textarea input processing, though it does not explicitly differentiate from potentially similar tools like 'get_data_from_user_uploaded_files'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. Among many sibling tools, there is no mention of context or exclusions, leaving the agent without clear decision 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/OnStartups/agentai-mcp-server'

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