Skip to main content
Glama
Sign In
tuskr-mcp

tuskr-mcp

by Zapkid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_test_suite

Create a new test suite (main folder) in a Tuskr app. Requires app name and suite name; optionally include a description or retrieve an existing suite.

Instructions

Create a Tuskr test suite (main folder).

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": {
      "app_name": "<app_name>",
      "suite_name": "<suite_name>"
    },
    "name": "create_test_suite"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_nameYes
suite_nameYes
descriptionNo
create_or_getNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations provided, and the description fails to disclose behavioral details such as what happens if the suite already exists, the effect of the 'create_or_get' parameter, authentication requirements, or idempotency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, making it very concise. However, it is too brief to provide adequate information, sacrificing clarity for brevity.

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

Completeness2/5

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

With four parameters, no annotations, and an output schema present, the description lacks details about return values, error scenarios, and parameter relationships. It is incomplete for effective use.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no explanation for any of the four parameters (app_name, suite_name, description, create_or_get). It does not compensate for the lack of schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'Create a Tuskr test suite (main folder)' with a specific verb and resource, and 'main folder' distinguishes it from create_section which likely creates subfolders. However, it could more explicitly clarify the exact scope.

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?

No guidance on when to use this tool versus alternatives like create_section (for subfolders) or any prerequisites. The description omits usage context entirely.

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