Skip to main content
Glama
Sign In

Testsy

by dev.testsy
OverviewDiscussionsAdmin

Find a build

find_build
Read-only

Is this build already uploaded? Looks up the project's newest ready build by the file's sha256, else by a native fingerprint; build is null when neither matches. A sha256 match means the exact file is uploaded: run it with run_test {buildId} / run_project {buildIds} instead of uploading again. A fingerprint match (a hash of the native inputs the uploader stored with the build, for example @expo/fingerprint) means the native build is unchanged, so CI can skip building it. The command-line tool does this for files: qa-ai build find / build ensure.

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": {
      "projectId": "<projectId>"
    },
    "name": "find_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
sha256Nosha256 of the build file, 64 hex characters
projectIdYesProject id (p_…)
fingerprintNoNative fingerprint stored with the build (8–128 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The readOnlyHint=true and openWorldHint=false annotations are consistent with a pure lookup, and the description adds real behavior beyond them: only *newest ready* builds are considered, sha256 takes precedence over fingerprint, and the result is null when nothing matches. That precedence and null semantics are exactly what an agent needs to interpret a response.

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?

The leading question front-loads intent, and the sha256-then-fingerprint ordering mirrors the lookup logic. Every sentence carries information, though the trailing CLI mapping (qa-ai build find / build ensure) is marginally useful for an API-calling agent and could be trimmed.

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

Completeness5/5

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

There is no output schema, so the description carries the return-value burden and does so: it names the returned build, its null case, and the meaning of each match. For a three-parameter read-only lookup, nothing needed to call or interpret it is missing.

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?

Schema coverage is 100%, so the baseline would be 3, but the description goes further by explaining what a match on sha256 (exact file already uploaded) versus fingerprint (hash of native inputs stored with the build, e.g. @expo/fingerprint) actually means. Only projectId gets no extra narrative beyond the schema's own p_… hint.

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?

The description opens with a specific question form ("Is this build already uploaded?") then states the exact operation: look up the project's newest ready build by sha256, falling back to native fingerprint. It distinguishes itself from sibling run_test/run_project and from uploading, so an agent can place it without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use conditions for both lookup modes: a sha256 hit means run with run_test {buildId} / run_project {buildIds} instead of re-uploading, and a fingerprint hit means CI can skip building. The null case (neither matches) is also stated, so the agent knows what a miss implies.

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

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

Resources