Skip to main content
Glama
nyku

Competiflow MCP Server

by nyku
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create workspace

create_workspace

Create a workspace for a product or market and set product_url to your own product so changes are explained relative to it. Returns 422 when your plan's workspace limit is reached.

Instructions

Create a workspace for one product or market. Set product_url to your own product so why_it_matters explains each change relative to it. Returns 422 when your plan's workspace limit is reached. To rename or change an existing workspace, use update_workspace.

Input Schema

NameRequiredDescriptionDefault
nameYesWorkspace name, e.g. the product or market it covers
product_urlNoYour own product's URL (e.g. example.com). The server adds https:// when missing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / name / description
      Previous value: -"Workspace name"New value: +"Workspace name, e.g. the product or market it covers"
    • addedInput schema / properties / product_url
      Added value: +{
+  "description": "Your own product's URL (e.g. example.com). The server adds https:// when missing.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare non-readonly, non-idempotent, non-destructive, so the safety profile is covered. The description adds genuinely non-structured context: a plan-based workspace cap that surfaces as HTTP 422, and why product_url changes downstream output (why_it_matters). It stops short of saying what the call returns on success.

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?

Four short sentences, front-loaded with the core action, then the param rationale, then the failure mode, then the sibling routing. No filler or restated title.

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?

There is no output schema, so the description carries the return-value burden and only partially meets it — it discloses the 422 failure but not the shape of a successful response (e.g. workspace id). For a 2-param creation tool the rest of what an agent needs is present.

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 baseline is 3. The description goes beyond the schema by explaining the purpose of product_url — it makes why_it_matters explain each change relative to your product — which is motivation the schema text does not carry.

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 workspace") plus the scoping unit ("one product or market"), which immediately distinguishes it from list/update/delete siblings. An agent can tell what it produces without opening the schema.

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 routes the alternative case away: "To rename or change an existing workspace, use update_workspace." It also gives conditional guidance for the optional param (set product_url to your own product). Both when-to-use and when-not-to-use are present.

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

Deploy Server

Other Tools