Skip to main content
Glama

create_server

Creates a new communication server visible to all accounts and returns a serverId for creating channels where local AI sessions can exchange messages.

Instructions

Creates a new communication server (visible to all accounts). Create channels with the returned serverId.

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_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesServer name (max 64 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv2.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a non-readonly, non-destructive, non-idempotent write in a closed world. The description adds context the annotations do not: the created server is visible to all accounts (a visibility/side-effect disclosure) and that it returns a serverId consumed by create_channel. It stops short of noting consequences such as duplicate names spawning multiple servers, which would matter given idempotentHint=false.

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 short sentences, front-loaded with the core action and followed by the immediately actionable next step. Every clause carries information an agent needs; nothing is padded or repeated from the annotations.

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 simple one-parameter, non-destructive creation tool with no output schema, the definition covers purpose, visibility scope, and the practical value of the return value (serverId). It could be marginally stronger by stating that repeated calls create additional distinct servers, but nothing essential to calling it correctly is missing.

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% and the single 'name' parameter already documents its string type and 64-character max, so the description adds no syntax or constraint meaning beyond the schema. Baseline 3 is appropriate for a one-parameter tool whose schema does the documentation work.

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 new communication server') plus a scope qualifier ('visible to all accounts'), so the agent knows exactly what is produced. Sibling names like create_channel make the distinction clear without the description needing to name them explicitly.

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?

The second sentence gives useful sequencing guidance — create channels using the returned serverId — which effectively tells the agent this is a prerequisite step for channel creation. However, there is no explicit when-to-use/when-not guidance, no mention of preconditions (e.g., which account is acting), and no comparison to alternatives such as open_dm or list_servers.

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