Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

Create a workspace

connections_create_workspace
Idempotent

Create a new workspace on the signed-in account when the member asks for one. A name close to an existing one creates nothing and lists the candidates: ask the member, then switch to the existing one or call again with confirm:true. An exact name creates nothing and returns the existing workspace. A 402 means their plan does not include another workspace: tell them what it says. To work in the new workspace, call connections_switch_workspace with its companyId.

Input Schema

NameRequiredDescriptionDefault
nameYesThe workspace name, e.g. 'Ask Susie'.
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
confirmNoCreate even though a similarly named workspace exists. Set it only after the member says so.
projectNoWorkspace to run this call in (id or name).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / person
      Added value: +{
+  "description": "Linked person to run this call as (first name). Omit to run as the connection's holder.",
+  "type": "string"
+}
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world, and the description reinforces and extends that: an exact name creates nothing and returns the existing workspace, a close name returns candidates instead of writing, and a 402 signals a plan limit. These are consequential failure-mode details an agent could not infer from the schema or annotations.

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?

Purpose is front-loaded in the first clause, and each subsequent sentence handles a distinct case (near-match, exact match, 402, next step) with no filler. Dense but every sentence earns its place.

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?

For a mutating tool with no output schema, the description covers the happy path, the two non-creating outcomes, the billing failure, and the required follow-up call. Nothing an agent needs to invoke 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%, so the baseline is 3, but the description adds real meaning: it explains the workflow for confirm (ask the member first, then retry with confirm:true) and the distinction between close and exact name matches. It says less about person and project, which the schema already covers adequately.

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 workspace on the signed-in account") with clear scope. It implicitly separates itself from connections_switch_workspace, which it names as the follow-up action rather than the creation tool.

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?

Explicitly says when to call it ("when the member asks for one") and what to do in the tricky cases: near-duplicate name, exact-name match, and a 402 plan limit. It routes to the sibling tool (connections_switch_workspace) for the next step.

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

All Connections toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources