Skip to main content
Glama

create_mcp_server

Add a new outbound MCP server configuration and attempt to connect. Use when the user wants Ballet playbooks to call tools from another MCP server.

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>",
      "transport": "<transport>",
      "url": "<url>"
    },
    "name": "create_mcp_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
nameYes
headersNoOptional HTTP headers
transportYes"http" or "sse"

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the agent knows this is a non-destructive write with external reach. The description adds that a connection attempt occurs, which is useful beyond the annotations, but it does not say whether the config persists if the connection fails or what error behavior to expect.

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 action and followed by the usage condition. No wasted wording.

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 mutation tool with no output schema and a nested headers object, the description covers the action and the trigger but omits failure semantics, persistence behavior, and any parameter detail. Adequate to start a call, not complete enough to predict outcomes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: transport and headers are documented in the schema, but name and url are not. The description adds no meaning to any parameter, so it fails to compensate for the undocumented fields on a 4-parameter tool with a nested headers object.

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 ('Add a new outbound MCP server configuration') plus a secondary effect ('attempt to connect'). It is distinguishable from siblings like get/update/delete_mcp_server, though the 'attempt to connect' clause overlaps conceptually with connect_mcp_server and the description does not clarify the boundary.

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?

Gives a clear when-to-use condition: 'Use when the user wants Ballet playbooks to call tools from another MCP server.' It does not state exclusions or point to connect_mcp_server for servers that already exist, so the routing guidance is clear but incomplete.

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