Skip to main content
Glama

TestChimp

by io.testchimp
OverviewDiscussionsAdmin

Get Release

get-release
Read-onlyIdempotent

Fetch or list releases in the current project. Pass version for one release; set detail=GATE for gate-oriented details (scope, per-environment priority×status test stats, open issue stats, scan summaries, in-scope scenario/issue records). Omit version to list: optional environment, pageSize, pageToken, excludeArchived. Authenticated via project API key.

Input Schema

NameRequiredDescriptionDefault
botIdNoQA bots: your botId from your stored TestChimp binding.
detailNo
versionNo
pageSizeNo
pageTokenNo
environmentNo
projectApiKeyNoQA 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.
excludeArchivedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
+  "enum": [
+    "CATALOG",
+    "GATE",
+    "MCP_RELEASE_VIEW_CATALOG",
+    "MCP_RELEASE_VIEW_GATE",
+    "MCP_RELEASE_VIEW_UNSPECIFIED"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / environment
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / excludeArchived
      Added value: +{
+  "type": "boolean"
+}
    • addedInput schema / properties / pageSize
      Added value: +{
+  "exclusiveMinimum": 0,
+  "maximum": 200,
+  "type": "integer"
+}
    • addedInput schema / properties / pageToken
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "version"
-]
  2. Changed2 schema fields changed
    • 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"
+}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real value beyond that: it states the auth mechanism ('Authenticated via project API key') and enumerates what the GATE detail payload contains (scope, priority×status stats, open issue stats, scan summaries). It omits rate limits and output shape, but that is acceptable given the annotation coverage.

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 dense clauses with zero filler, front-loaded by mode. The parenthetical payload list earns its space by telling the agent what GATE returns, which it otherwise could not know without an output schema.

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

Completeness3/5

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

For an 8-parameter tool with no output schema and 25% schema coverage, the description covers modes and auth well but leaves several decision-relevant gaps: the unexplained MCP_RELEASE_VIEW_* enum values, excludeArchived semantics, and pagination behavior. Adequate to call it, not adequate to call it confidently in edge cases.

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

Parameters2/5

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

Schema coverage is only 25%, so the description must compensate, and it does so only partially: it explains version and detail=GATE and name-drops environment, pageSize, pageToken, excludeArchived as list options. It never explains environment's meaning, excludeArchived's default/behavior, pageSize limits, or the CATALOG and MCP_RELEASE_VIEW_* enum values that an agent would face in the schema.

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?

Starts with a concrete verb+resource ('Fetch or list releases in the current project') and immediately splits the tool's two operating modes (single release via version, list via omitted version). An agent can distinguish this from upsert-release purely from the read-oriented verb framing.

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?

Explicit routing rules: pass version for one release, set detail=GATE for gate-oriented output, omit version to list. That covers the main decision fork. It never names a sibling alternative (e.g. upsert-release for writes), so it stops short of full when/when-not guidance.

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

All TestChimp toolsInspect
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.

Resources