Skip to main content
Glama
Sign In
Lucius

Lucius

by ivanostanin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Manage Test Plan Content

manage_test_plan_content
DestructiveIdempotent

Update an existing test plan by adding or removing test cases using their IDs, or modify the AQL filter query to refine which test cases are included.

Instructions

Modify the content (Test Cases) of an existing Test Plan.

Allows adding or removing specific Test Cases by ID, or updating the underlying AQL filter query.

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": {
      "plan_id": "<plan_id>"
    },
    "name": "manage_test_plan_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesID of the test plan
output_formatNoOutput format: 'json' (default) or 'plain'.
add_test_case_idsNoList of Test Case IDs to add
update_aql_filterNoUpdate the AQL filter string
remove_test_case_idsNoList of Test Case IDs to remove

Output Schema

NameRequiredDescriptionDefault
urlNo
plan_idNo
aql_filterNo
add_test_case_idsNo
add_test_case_urlsNo
remove_test_case_idsNo
remove_test_case_urlsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.14.0
  2. Removedv0.12.1
  3. First observedv0.11.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate destructive (destructiveHint=true) and idempotent behavior. The description adds value by enumerating the three types of modifications (add, remove, update filter), which is beyond what annotations provide. No contradictions with annotations.

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?

Two sentences, front-loaded with the core action. Every sentence adds value with no fluff. The structure efficiently conveys the tool's purpose and capabilities.

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?

Given the tool's complexity (5 parameters, output schema present, annotations), the description covers the main operations. However, the 'or' in 'adding or removing... or updating' could be misinterpreted as mutually exclusive, whereas the schema allows combining operations. Minor ambiguity keeps it from being a 5.

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% with clear descriptions for each parameter. The tool description groups the parameters into operations but does not add new constraints or details beyond the schema. Baseline score of 3 is 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 clearly states 'Modify the content (Test Cases) of an existing Test Plan' and lists specific operations: adding/removing Test Cases by ID or updating the AQL filter. This distinguishes it from sibling tools like update_test_plan which likely handles other attributes.

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?

The description clearly indicates when to use the tool (modifying test plan content) but does not explicitly mention alternatives or when not to use it. The specificity of operations provides implicit guidance, but explicit exclusion of other update tools would improve clarity.

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