Skip to main content
Glama
gabriel-tbc

qa-toolkit-mcp

by gabriel-tbc

qa_get_run

Read-onlyIdempotent

Retrieve a specific test run by ID, with the option to include passed tests and choose between Markdown or JSON output.

Instructions

Return a single test run by id.

By default, only failed/error tests are listed in the body (to keep context
small). Set `include_passed=true` for the full inventory.

Returns:
    Markdown or JSON depending on response_format. JSON returns the full
    RunReport model conforming to schemas/run-report.v1.json.

Error response: string starting with "Error: ..." (e.g., "Error: Run not found").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idYesExact run_id (file stem, no extension).
include_passedNoIf true, include passed tests in the output. Default false to keep context small.
response_formatNo'markdown' for human-readable, 'json' for programmatic.markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds details about error responses and default test inclusion, providing useful extra context beyond annotations.

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 concise with three short paragraphs: purpose, parameter guidance, and return/error info. No unnecessary words, well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple retrieval nature, annotations, and full schema coverage, the description provides all necessary context including error response format and reference to output schema. Complete for the tool's complexity.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining the default behavior of include_passed and the return format options, 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 'Return a single test run by id' with a specific verb and resource. It is easily distinguishable from sibling tools qa_list_runs and qa_compare_runs.

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 explains when to use include_passed and response_format parameters, but does not explicitly contrast with siblings. It provides clear context on default behaviors, which is helpful.

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/gabriel-tbc/qa-toolkit-mcp'

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