testit-mcp-server

search_test_points

Read-only

Search test points across test plans and test suites by status, tester, plan/suite ID, configuration, or raw filter, with paging and sorting.

Instructions

Search test points across test plans/suites. Typed fields are merged with an optional raw "filter" (TestPointFilterRequestModel).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_test_points"
  }
}

Input Schema

Name	Required	Description
`name`	No
`page`	No	1-based page number; alternative to skip. Uses "size" (default 50).
`size`	No	Page size for "page"; alias of take.
`skip`	No	Number of items to skip (offset).
`take`	No	Max number of items to return.
`filter`	No
`orderBy`	No	Sort expression, e.g. "createdDate desc".
`statuses`	No
`testerIds`	No
`searchField`	No	Field name to search in.
`searchValue`	No	Value to search for in searchField.
`testPlanIds`	No
`testSuiteIds`	No
`configurationIds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

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 useful behavioral detail that typed fields are merged with an optional raw filter, but it does not disclose pagination behavior, result shape, or filter precedence rules.

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?

The description is two concise sentences with no wasted wording. The core purpose is front-loaded and the filter merging behavior is stated directly.

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?

This is a complex search tool with 14 parameters, a nested filter object, and no output schema. The description is too terse to fully cover that surface area, especially the raw filter structure, typed-field merge behavior, and result handling.

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 description coverage is only 50%, so the description should compensate more than it does. It adds valuable meaning for the ambiguous filter parameter by naming TestPointFilterRequestModel and explaining that typed fields are merged with it, but most other parameters receive no additional semantics in the description.

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 uses a specific verb and resource: search test points across test plans/suites. It is clear what the tool does, though it does not explicitly distinguish itself from sibling search/list tools such as list_test_suite_test_points.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'across test plans/suites' implies this is for cross-plan or cross-suite search rather than suite-local listing, but no explicit when-to-use or when-not-to-use guidance is given. Alternatives are not named.

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

Deploy Server