Skip to main content
Glama

TestChimp

by io.testchimp
OverviewDiscussionsAdmin

List Screen States

list-screen-states
Read-onlyIdempotent

Fetch the project's screen/state vocabulary (relational atlas) for SmartTests and traces. Optional environment field is accepted for forward compatibility; v1 may be project-global.

Input Schema

NameRequiredDescriptionDefault
botIdNoQA bots: your botId from your stored TestChimp binding.
platformNo
environmentNo
endCommitShaNo
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.
startCommitShaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / endCommitSha
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / platform
      Added value: +{
+  "enum": [
+    "web",
+    "ios",
+    "android"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / startCommitSha
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
  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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior. The description adds useful behavioral context about environment being accepted only for forward compatibility and possibly being project-global in v1, but it does not cover return format, pagination, or other operational traits.

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 efficient sentences with zero filler, and the primary purpose is front-loaded before the caveat about environment.

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 a read-only list tool with annotations covering safety and no output schema, the description is adequate but incomplete. It does not explain what the commit range or platform filters do, which matters for correct invocation with six available parameters.

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 low (33%), so the description should compensate. It adds meaningful semantics for the ambiguous 'environment' parameter, explaining that it is optional and may not actually scope results in v1, but it leaves platform and the commit SHA range parameters unexplained beyond the schema.

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 uses a specific verb ('Fetch') and resource ('screen/state vocabulary'), and clarifies scope as project-level for SmartTests and traces. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling upsert-screen-states tool.

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?

The phrase 'for SmartTests and traces' implies the context in which to use it, but there is no explicit when-to-use or when-not-to-use guidance relative to alternatives. The note about the environment field hints at current limitations but does not provide selection 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