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

testit-mcp-server

by iampopovich
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_configuration_parameter

Read-only

Retrieve a configuration parameter by UUID, including its values and associated projects, to inspect test management settings.

Instructions

Get a configuration parameter with its values and projects.

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_parameter"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesConfiguration parameter UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/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 the safety profile is covered. The description adds that the result carries nested values and projects, which is useful context, but says nothing about not-found behavior, permissions, or field completeness.

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?

A single nine-word sentence with zero filler, front-loading the action and resource and appending the returned payload. Nothing is repeated or wasted.

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?

For a simple single-entity read with one fully documented parameter and no output schema, the description covers the essential shape of the return (values and projects). Only minor behavioral details, such as how a missing id is handled, are absent.

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 exactly one parameter with 100% schema description coverage ('Configuration parameter UUID'), so the schema already does the work. The description adds no syntax, format, or scoping detail about the id beyond what the schema states.

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?

States a specific verb and resource (get a configuration parameter) and adds that the response includes the parameter's values and projects, which hints at an expanded representation. It does not explicitly distinguish itself from the sibling search_configuration_parameters, so an agent must infer that this is single-item retrieval by id.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as search_configuration_parameters for lookups that are not by UUID. The only implied signal is the required id argument in the schema.

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