Skip to main content
Glama

Create a named list

create_list

Creates a named membership list (a new list). Does not use credits. add_to_list adds project ids to it.

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
nameYesList name the user chose.
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the mutation profile is covered. The description adds one genuinely useful behavioral fact beyond the annotations — it does not consume credits — but says nothing about failure modes, duplicate-name handling, or what identifier the new list receives.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action and no padding. The parenthetical restatement and the slightly clipped final sentence cost a point but nothing is wasteful.

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 simple two-parameter creation tool with no output schema, the description is adequate but leaves one practical gap: it never says what the call returns (e.g., the new list's id), which the agent likely needs to pass to add_to_list. Otherwise complexity is low enough that no further disclosure is required.

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 50%: "name" is documented in the schema while "description" is not, and the description does not compensate for that gap. It only echoes the notion of a named list, adding no constraint or format guidance beyond the schema.

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?

States a specific verb and resource ("Creates a named membership list") and clarifies it makes a new, empty list rather than adding to an existing one. The mention of add_to_list further pins down the boundary with that sibling, though the parenthetical "(a new list)" is slightly redundant with the name/title.

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

Usage Guidelines3/5

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

Implies usage as the first step before add_to_list adds project ids, and the "Does not use credits" note helps an agent decide whether to call it. However, there is no explicit statement of when not to use it (e.g., list already exists) or what happens on duplicate names.

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