Skip to main content
Glama

Create a list

create_list

Use this when the user wants a new, empty list to collect people (the default) or companies in. The kind cannot change later, and a name another list already has is refused. Free. It adds nobody: people are put on the list afterwards.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe list's name. A name another list of the organization has is refused.
typeNoWhat the list's rows are: people (the default) or companies. It cannot change later.people

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the write/non-destructive/non-idempotent profile; the description adds real context on top: the kind is immutable after creation, duplicate names are refused, and the call is free. It stops short of saying what the response contains, but the mutation semantics are well covered.

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?

Four compact sentences, front-loaded with the trigger, each carrying distinct information (default kind, immutability, name conflict, cost, no members). Nothing is redundant or padded.

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?

For a 2-parameter creation tool with no output schema, the description covers the trigger, defaults, immutability, conflict behavior, and cost. Only the shape of the returned object (e.g., the new list's identifier) is left unstated, a minor gap.

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 coverage is 100%, so both name and type are already documented, including the name-uniqueness rule and the immutability of type. The description restates those constraints rather than adding new meaning, so the baseline 3 is appropriate.

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?

States a specific verb and resource (create a new, empty list) plus its scope (collecting people by default, or companies). The empty-list framing plus the enum distinguishes it from add_people_to_list and list_lists without needing the schemas.

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

Usage Guidelines4/5

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

Opens with an explicit when-to-use trigger ('when the user wants a new, empty list') and clarifies the boundary that it adds no members, so people are put on the list afterwards. It doesn't name the follow-up sibling explicitly, which keeps it from a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources