Skip to main content
Glama

Create a workspace

create_workspace

Create a Sinatra workspace and make you its owner. Use it when whoami lists no workspaces. It starts with no integrations: next, call connect_integration with integration "github" and give the person the URL it returns: the dashboard page where they install the Sinatra GitHub App and pick repositories. Each person can create one workspace this way; if they already have one without GitHub, use that one. Does not take workspace_id.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe workspace's name, often the person's team or company: 1–120 letters, numbers, spaces and basic punctuation, with no web address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (non-read-only, non-destructive, non-idempotent), it discloses what is created: the caller becomes owner, the workspace starts with no integrations, and each person is limited to one workspace created this way. It also rules out a workspace_id argument, heading off a likely calling error.

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?

Front-loads the core action and the trigger before the onboarding sequence. The connect_integration hand-off runs a bit long for a create tool, but every clause carries actionable routing or constraint information.

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

Completeness5/5

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

No output schema exists, yet the description tells the agent what to do next and what connect_integration returns (a dashboard URL to hand to the person). For a one-parameter create tool, nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% and the schema already specifies the name format and constraints, so the description does not need to restate them. It does add one useful semantic note, that no workspace_id is accepted, which steers the agent away from passing an identifier.

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 Sinatra workspace') plus a side effect ('make you its owner'), and distinguishes itself from connect_integration and whoami by naming both.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Use it when whoami lists no workspaces'), an exclusion ('if they already have one without GitHub, use that one'), and the follow-up routing to connect_integration with the github argument.

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