Skip to main content
Glama

Krate

Check a Krate build

build_status

The state of a Krate build, by its build id: still building, failed, or published. A failed build's answer has Krate's check in its own words: the stage, what went wrong and how to fix it. A published build's answer has the app's link and a browser link that opens it on any device, nothing to install. Needs the person to sign in to Krate.

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": {
      "build_id": "<build_id>"
    },
    "name": "build_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
build_idYesThe build id a build answered with

Output Schema

NameRequiredDescriptionDefault
fixNoHow to fix it, in the check's own words
linkNoThe app's own link; it opens the newest version
nameNo
stageNoWhere Krate's check stopped, on a failure
app_idNo
detailNoWhat went wrong, in the check's own words
statusYes
messageYes
build_idYes
browser_linkNoOpens the app in a browser on any device, nothing to install

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 the safety profile (destructiveHint=false, openWorldHint=false), so the description's real value-add is the auth requirement and the shape of failure and published answers. Those details are genuinely useful. It doesn't disclose pagination, latency, or whether a build id that never existed yields an error, so it adds context but not rich behavioral depth.

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 answer states the states and their enriched results first, then the auth prerequisite, with almost no filler. Some of the failure and published answer detail overlaps with what the output schema presumably conveys, but it stays short and well-front-loaded.

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?

An output schema exists and annotations cover safety, so the description needn't explain return shapes; it still notes auth and the failure and published cases. For a single-parameter status lookup this is essentially complete, with only sibling routing left out.

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?

There is one parameter with 100% schema coverage, so the baseline is 3; the schema already defines build_id's 32-character constraint and origin. The description only echoes "by its build id" without adding format, sourcing, or error semantics 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?

States a specific verb and resource ("The state of a Krate build, by its build id") and enumerates the possible outcomes (building, failed, published), so the agent knows exactly what it gets back. It never contrasts itself with siblings like get_app or build_app, so it earns a 4 rather than a 5.

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 definition implies usage through "by its build id" and adds the prerequisite that the person must sign in to Krate, which is actionable context. It gives no explicit when-to-use or when-not-to-use guidance against build_app, get_app, or list_featured, leaving the agent to infer selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.