TestChimp

List Perf Runs

list-perf-runs

Read-onlyIdempotent

List performance runs, optionally filtered by TestChimp id, JOURNEY/COMPOSITE kind, branch, profile, dataset, LLM mode, or environment. Pass runId to fetch one run (optional includeRaw for the raw payload).

Input Schema

Name	Required	Description
`kind`	No
`botId`	No	QA bots: your botId from your stored TestChimp binding.
`limit`	No
`runId`	No
`offset`	No
`dataset`	No
`fileIds`	No
`llmMode`	No
`profile`	No
`release`	No
`branchName`	No
`folderPath`	No
`includeRaw`	No
`environment`	No
`testchimpId`	No
`groupByBatch`	No
`projectApiKey`	No	QA bots: your own project API key from your stored TestChimp binding. Required on every call except get-bot-credentials, get-project-credentials and get-bot-compat. Never print it.
`batchInvocationId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 22, 2026

addedInput schema / properties / batchInvocationId

Added value: +{
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / fileIds

Added value: +{
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / folderPath

Added value: +{
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / groupByBatch
```
Added value: +{
+  "type": "boolean"
+}
```
addedInput schema / properties / includeRaw
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / release

Added value: +{
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / runId

Added value: +{
+  "minLength": 1,
+  "type": "string"
+}

Changed2 schema fields changedOct 5, 2026

addedInput schema / properties / botId

Added value: +{
+  "description": "QA bots: your botId from your stored TestChimp binding.",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / projectApiKey

Added value: +{
+  "description": "QA bots: your own project API key from your stored TestChimp binding. Required on every call except get-bot-credentials, get-project-credentials and get-bot-compat. Never print it.",
+  "maxLength": 256,
+  "minLength": 8,
+  "type": "string"
+}

First observedOct 5, 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, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that includeRaw returns the raw payload and that runId fetches one run, but it does not mention pagination defaults, result ordering, or auth requirements beyond what the schema fields already state.

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 tight sentences with no filler. The main list operation is front-loaded, followed by the single-run mode and includeRaw option.

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?

For an 18-parameter tool with low schema description coverage and no output schema, the description is incomplete. It covers the main filters and single-run fetch, but it omits pagination semantics, default behavior, grouping options, and return-shape guidance that would help an agent call this complex listing tool correctly.

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 11%, so the description must compensate. It explains the meaning of many filters (testchimpId, kind, branch, profile, dataset, llmMode, environment, runId, includeRaw), but it leaves several parameters unexplained, including limit, offset, fileIds, release, folderPath, groupByBatch, and batchInvocationId.

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 clearly states the verb and resource: it lists performance runs and can fetch a single run by runId. It distinguishes the resource type from siblings like list-perf-baselines or list-related-perf-tests, but does not explicitly name those alternatives.

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?

It gives useful usage context for filtering and for the runId single-fetch mode, but it does not explain when to choose this tool over close siblings such as list-perf-baselines, list-related-perf-tests, compare-perf-to-baseline, or fetch-execution-report. The guidance is implied rather than explicit.

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

All TestChimp tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

List Perf Runs

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources