testit-mcp-server

get_configuration

Read-only

Retrieve a TestIT configuration by its UUID to inspect settings for test management workflows.

Instructions

Get a configuration by ID.

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": "get_configuration"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Configuration UUID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-visibility characteristics are covered. The description adds nothing further, such as behavior when the ID is unknown (error vs empty), whether results are cached, or what fields a configuration contains. With annotations carrying the safety profile, a 3 is appropriate.

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

Conciseness4/5

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

A single short sentence front-loads the verb and resource with no wasted words. It is efficient, though so terse that it borders on under-specification rather than maximum informativeness.

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?

For a one-parameter read tool with full schema coverage and annotations, the definition is minimally sufficient to invoke correctly. It omits what a configuration represents and the not-found behavior, which are minor but real gaps for an agent choosing among many sibling get_* tools.

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?

There is a single required parameter with 100% schema description coverage ("Configuration UUID"), so the schema does the heavy lifting. The description's "by ID" aligns with but does not enrich the schema — no format, sourcing, or example values are added.

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?

The description states a specific verb and resource ("Get a configuration") plus the lookup key ("by ID"), so an agent knows exactly what the tool retrieves. It does not differentiate from sibling reads such as get_configuration_parameter or search_configuration_parameters, leaving the boundary between them implicit.

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 alternatives for listing or searching configurations, and no note that the ID must refer to an existing configuration. The agent must infer usage entirely from the name and schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server