TestChimp

Upsert Plans Support File

upsert-plans-support-file

DestructiveIdempotent

Create or update any file under the mapped plans root on the platform by relative path (no git commit/push required). Primary use: upload workflow execution plans at knowledge/workflow_plans//<workflow_execution_id>.plan.md after the Plan phase. filePath is relative to the plans mapped root (leading plans/ is stripped). Under workflow_plans/, filenames are coerced to *.plan.md and stored as WORKFLOW_EXECUTION_PLAN. Response includes supportFileId, filePath (canonical), filetype, created. Blocking step before Execute for cloud agents.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "filePath": "<filePath>",
      "content": "<content>"
    },
    "name": "upsert-plans-support-file"
  }
}

Input Schema

Name	Required	Description
`botId`	No	QA bots: your botId from your stored TestChimp binding.
`content`	Yes
`filePath`	Yes
`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.

Schema Changelog

Changes observed during successful MCP inspections.

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

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint, idempotentHint, and openWorldHint; the description adds useful context beyond that – storage type (WORKFLOW_EXECUTION_PLAN), filename coercion, canonical path normalization, and the returned fields. It could more explicitly note the overwrite/destructive behavior on existing files, which is only implied by 'update'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then primary use, normalization rules, response shape, and workflow gating. Information-dense and mostly earning its place, though the return-fields sentence is a slight tack-on given no output schema.

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 a mutation tool with no output schema, the description covers what it does, where files land, normalization behavior, and the returned keys, plus auth params are documented in the schema. It falls just short of explicitly stating overwrite/destructive semantics for an upsert.

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?

With 50% schema coverage, the description meaningfully compensates: it explains that filePath is relative to the plans mapped root, that a leading 'plans/' is stripped, and that filenames under workflow_plans/ are coerced to *.plan.md. This adds real semantics beyond the schema, though the required 'content' parameter remains undocumented.

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?

States a specific verb+resource: create/update a file under the mapped plans root by relative path. It also distinguishes itself from the sibling get-plans-support-file by specifying it writes rather than reads, and names the canonical workflow_plans location.

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?

Gives clear usage context ('Primary use: upload workflow execution plans... after the Plan phase' and 'Blocking step before Execute for cloud agents'). It stops short of naming explicit alternatives or when-not-to-use conditions, but the workflow-phase framing is quite actionable.

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.