Skip to main content
Glama

studio_preflight

Run a read-only preflight for a shot to report missing references and upstream tool compatibility before production, without checking live credits.

Instructions

Read-only per-account production preflight; reports missing references and upstream tool compatibility, never verifies live credits.

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>",
      "accountId": "<accountId>",
      "shotId": "<shotId>"
    },
    "name": "studio_preflight"
  }
}

Input Schema

NameRequiredDescriptionDefault
shotIdYes
accountIdYes
projectIdYes
probeUpstreamNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it declares read-only semantics, per-account scoping, and an explicit negative boundary ('never verifies live credits') that prevents a false assumption about credit validation. It does not describe behavior on failure or what a report looks like, but the safety profile and key limitation are covered.

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?

A single dense sentence that front-loads read-only and scope, then states outputs, then states the exclusion. Every clause carries information and nothing is padded.

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?

The description names the reported findings, which partly substitutes for the absent output schema, but with no annotations, no output schema, and zero parameter documentation, an agent still lacks the meaning of probeUpstream and the identifier parameters. Adequate for a read-only check, but with clear gaps.

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 0% across four parameters, so the description must compensate and largely does not. 'Per-account' loosely maps to accountId and 'upstream tool compatibility' hints at probeUpstream, but projectId, shotId, and the boolean probe flag's effect are never explained.

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 names a specific operation ('production preflight'), its scope ('per-account'), and its outputs ('missing references and upstream tool compatibility'), which lets an agent distinguish it from siblings like studio_status or studio_discover_upstream. It stops short of explicitly naming the sibling it supersedes, so it is clear but not sharply differentiated.

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?

'Preflight' implies use before a production dispatch, and 'never verifies live credits' hints at a separate credit-check path, but no when-to-use condition or alternative tool is stated outright. The agent must infer the sequencing from the word 'preflight' alone.

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