Skip to main content
Glama
TCSoftInc

TestCollab MCP Server

by TCSoftInc

get_test_plan

Retrieve a single test plan with summary details, including test case count, configurations, runs, and execution progress. Use by test plan ID or title.

Instructions

Fetch a single test plan with summary details:

  • Included test cases count

  • Test plan configurations

  • Test plan runs

  • Current execution progress status

Required: id or title Optional: project_id, include_configurations, include_runs, runs_limit, runs_offset, runs_sort

Example: { "id": 812, "project_id": 16 }

or

{ "title": "Release 3.0 Regression", "project_id": 16 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoTest plan ID to retrieve. Accepts numeric ID or title string.
titleNoTest plan title to retrieve (alternative to id).
project_idNoProject ID (uses default if not specified)
include_configurationsNoInclude test plan configurations in the response (default: true)
include_runsNoInclude test plan runs in the response (default: true)
runs_limitNoMaximum number of runs to return (1-100, default: 20)
runs_offsetNoNumber of runs to skip (default: 0)
runs_sortNoRun sort expression (default: "id:desc")id:desc
Behavior3/5

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

No annotations are provided, so the description bears full burden. It mentions the tool fetches data (read operation) and lists what is included, but does not disclose error handling, authentication requirements, rate limits, or what happens if the plan does not exist.

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 structured with a clear introductory sentence, bullet points listing included details, parameter guidance, and a code example. Every sentence earns its place with no redundancy or verbosity.

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 8 parameters (most with defaults), no output schema, and no annotations, the description covers core functionality and parameter usage well. It explains what the response includes (test cases count, configurations, runs, progress) but does not detail the response structure or error scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. The description adds value by stating that 'id' accepts numeric ID or title string, providing explicit examples, and clarifying optional parameters like include_configurations and include_runs, which goes beyond the schema descriptions.

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 'Fetch a single test plan with summary details' and enumerates specific included data. This distinguishes it from siblings like list_test_plans (which returns multiple) and get_test_case/get_suite (different resources).

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 specifies required parameters (id or title) and optional ones, with examples showing usage. While it doesn't explicitly compare with alternatives, the context of sibling tools and the phrase 'single test plan' implies when to use this versus list_test_plans.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TCSoftInc/testcollab-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server