Skip to main content
Glama
Sign In
testit-mcp-server

testit-mcp-server

by iampopovich
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_test_suite_configurations

Read-only

Retrieves all configurations for a test suite using its UUID so you can inspect and manage suite settings in TestIT.

Instructions

Configurations of a test suite.

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": {
      "id": "<id>"
    },
    "name": "list_test_suite_configurations"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTest suite UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no pagination behavior, no scoping or filtering semantics, no indication of whether all configurations or only overridden ones are returned.

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

Conciseness2/5

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

It is short, but the brevity reflects under-specification rather than economy of expression. There is a single fragment with no verb and no structure to front-load, so nothing meaningful is communicated efficiently.

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?

For a list tool with no output schema, the description should at least convey what comes back and how results are shaped. It leaves the return values, pagination, and relationship to the parent test suite entirely unstated.

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?

With one parameter and 100% schema description coverage, the schema already documents the id as a test suite UUID. The description implies the configurations belong to that suite but adds no format, filtering, or ordering detail beyond the schema, which is the baseline expectation.

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

Purpose2/5

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

The description "Configurations of a test suite" is a noun phrase that essentially restates the tool name with the verb stripped out. It never states that it lists or returns configurations, nor does it differentiate itself from siblings such as list_configurations, list_test_plan_configurations, or set_test_suite_configurations.

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?

There is no when-to-use guidance, no mention of when to prefer list_configurations or list_test_plan_configurations, and no prerequisite information. An agent must infer usage entirely from the tool name.

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