Skip to main content
Glama

Create a Capital Company workspace

create_workspace

Use this when someone without a Capital Company account wants one for their firm. Opens a Capital Company workspace, an account and the firm’s team. Needs no sign-in. Capital Company emails them a sign-in link.

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": {
      "email": "<email>",
      "fullName": "<fullName>",
      "teamName": "<teamName>"
    },
    "name": "create_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe email address the person will sign in with
fullNameYesThe person’s full name
teamNameYesThe name of their firm or team, which the workspace is named after

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, it adds meaningful behavioral context: no sign-in is required, multiple resources are created, and Capital Company emails a sign-in link. It does not cover edge cases like duplicate emails, but the key auth and side-effect details are present.

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?

Three short sentences, front-loaded with the usage condition and followed by the essential effects. Every sentence carries useful information without repetition.

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 an unauthenticated, open-world creation tool with no output schema, the description covers who it is for, what gets created, and the email follow-up. Minor gaps around duplicate-account behavior or failure modes keep it from being fully exhaustive.

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%, so the parameter meanings are already fully documented. The description adds no parameter-specific syntax or constraints beyond the schema, making the baseline score appropriate.

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?

The description uses specific language to say it opens a workspace, an account, and the firm’s team for someone without a Capital Company account. This clearly distinguishes it from sibling tools like create_fund, invite_investors, and claim.

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?

It gives a clear triggering condition: use when someone without a Capital Company account wants one for their firm. It does not explicitly name alternatives or exclusion cases, but the context is strong enough for an agent to route correctly.

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