Skip to main content
Glama

clawbridge_preflight

Validates a registered project's static configuration before task submission, catching issues early without starting a worker or making network changes.

Instructions

Validate a registered project’s static configuration before task submission. This M1 check does not start a worker or make network changes.

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": "clawbridge_preflight"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and usefully discloses that this check does not start a worker or make network changes. It does not state whether the operation is read-only, what permissions are required, what happens on validation failure, or whether repeated calls are safe.

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?

Two concise sentences with no wasted wording. The purpose and the non-effect constraints are front-loaded and easy to scan.

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 simple one-parameter validation tool with no output schema, the description covers purpose, timing, and major side-effect exclusions. It remains incomplete on parameter sourcing and on the meaning or consequences of validation failure.

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 description coverage is 0%, so the description must compensate for the single projectId parameter. It only implies that the ID must refer to a registered project; it does not explain the expected format, where to obtain the ID, or what an invalid ID does.

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: validate a registered project’s static configuration, with timing before task submission. It does not explicitly name a sibling alternative such as clawbridge_submit, so it falls short of full sibling differentiation.

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 "before task submission" gives a clear when-to-use cue. However, it does not state when not to use the tool, name an alternative, or explain prerequisites beyond the project being registered.

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