Skip to main content
Glama
Sign In
tuskr-mcp

tuskr-mcp

by Zapkid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_test_cases_automated_bulk

Update the automated status for multiple test cases in bulk by specifying their keys or IDs. Toggle the automated field for selected cases.

Instructions

Set automated on multiple cases by key or id (automated field only).

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>",
      "case_keys_or_ids": "<case_keys_or_ids>",
      "automated": "<automated>"
    },
    "name": "set_test_cases_automated_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_nameYes
case_keys_or_idsYes
automatedYes
skip_missingNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states what the tool does (set automated field) but does not disclose behavioral traits such as idempotency, effect on other fields, error handling, rate limits, or return format. The output schema exists but is not referenced.

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 short sentence, which is concise but not optimally front-loaded. Every word is necessary but too much context is omitted; the sentence earns its place for purpose clarity but not for completeness.

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 4 parameters, 0% schema coverage, no annotations, and an output schema that is not explained, the description is insufficient. It does not provide enough context for an agent to correctly invoke the tool, such as how to format inputs or interpret results.

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?

The schema has 0% description coverage for its 4 parameters. The description adds minimal value: it hints that case_keys_or_ids accepts 'key or id' but does not clarify format (e.g., array of strings), and leaves app_name, automated, and skip_missing unexplained. The schema itself provides only type and default, so the description should compensate.

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 clearly states the verb 'set', the resource 'multiple cases', the specific field 'automated', and the method of identification 'by key or id'. It effectively distinguishes from the sibling tool 'set_test_case_automated' which operates on a single case.

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 provides no guidance on when to use this tool versus alternatives (e.g., set_test_case_automated), no prerequisites or exclusions, and no context on whether it complements other tools. The sibling list shows a singular version, but no comparison is made.

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