TestChimp

List API Operation Interactions

list-api-operation-interactions

Read-onlyIdempotent

List recorded API operation interactions. Requires testId and/or operationId. Defaults to REAL interactions; limit is capped at 100.

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": "list-api-operation-interactions"
  }
}

Input Schema

Name	Required	Description	Default
`botId`	No	QA bots: your botId from your stored TestChimp binding.
`limit`	No
`testId`	No
`retryCount`	No
`executionId`	No
`operationId`	No
`interactionId`	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.
`includePayloads`	No
`interactionType`	No		REAL

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 22, 2026

addedInput schema / properties / executionId

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

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

addedInput schema / properties / interactionId

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

changedInput schema / properties / interactionType / enum

Previous value: -[
-  "REAL",
-  "MOCKED"
-]New value: +[
+  "UNKNOWN_API_OPERATION_INTERACTION_TYPE",
+  "REAL",
+  "MOCKED"
+]

addedInput schema / properties / retryCount

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

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/idempotentHint/non-destructive, so safety is covered elsewhere. The description adds real behavioral facts — default filter is REAL and results are capped at 100 — but says nothing about pagination, ordering, or cost, and its 'requires testId and/or operationId' precondition contradicts the schema's zero required parameters.

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?

Three short sentences, each carrying distinct information (resource, precondition, defaults/caps), with the core purpose front-loaded. No filler.

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 a 10-parameter read tool with 20% schema coverage and no output schema, the description accounts for only a few parameters. Key filters such as executionId, interactionId, includePayloads, and retryCount are undocumented anywhere, and the stated precondition is inconsistent with the schema.

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 20% across 10 parameters, so the description carries heavy burden. It clarifies testId/operationId, the interactionType default of REAL, and the 100 cap on limit, but leaves executionId, interactionId, retryCount, includePayloads, and botId entirely unexplained.

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 ('List recorded API operation interactions'), which is clear on its own. It does not distinguish itself from the nearest sibling, get-api-operations, which an agent would plausibly confuse it with.

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?

'Requires testId and/or operationId' is the closest thing to a usage rule, giving the agent a precondition for calling. It names no alternatives and no when-not-to-use case, and the 'requires' claim conflicts with the schema where required parameters = 0.

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

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.