Skip to main content
Glama
Sign In
Survey Solutions MCP Server

Survey Solutions MCP Server

by lbruce-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

create_workspace

Set up a new Survey Solutions workspace with a unique name and display name. Requires admin_write permission.

Instructions

Create a new Survey Solutions workspace. Requires admin_write permission.

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": {
      "workspace_name": "<workspace_name>",
      "display_name": "<display_name>"
    },
    "name": "create_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNo
display_nameYes
workspace_nameYesLowercase letters/digits only, max 12 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.7

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It does disclose an authorization requirement, which adds useful context beyond the schema. However, it does not mention error behavior, persistence, duplicate-name handling, or response/return details.

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?

The description is two short sentences with no filler. The action is front-loaded, and the permission requirement is stated separately and clearly without unnecessary detail.

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?

The description is workable for a simple create operation with required parameters already present in the schema. However, with no output schema, no annotations, and no mention of error or return behavior, the agent must guess what happens after a successful or failed call, leaving notable gaps.

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 description coverage is only 33%; profile and display_name are not described in the schema, and the description adds no parameter-level explanation. Only workspace_name has constraints in the schema, leaving the agent with limited guidance for the other parameters.

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 a specific verb and resource: 'Create a new Survey Solutions workspace.' It clearly differentiates this from sibling workspace lifecycle tools like update_workspace, delete_workspace, enable_workspace, and disable_workspace.

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

Usage Guidelines2/5

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

The description states a prerequisite ('Requires admin_write permission') but gives no explicit guidance on when to use this tool versus alternatives. The agent must infer from the name that this is the creation operation and that updates would go to update_workspace.

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