Skip to main content
Glama
LCV-Ideas-Software

cross-review

by LCV-Ideas-Software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Check Submission Preflights (Legacy Alias)

session_truthfulness_preflight_check
Read-onlyIdempotent

Verifies session readiness before cross-review by checking all enabled runtime gates, preventing truthfulness-only false positives.

Instructions

Backward-compatible alias for session_preflight_check. Its top-level pass now reflects both enabled runtime gates, eliminating truthfulness-only false positives.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskNo
draftNo
callerYes
evidenceNo
session_idYes
response_formatNojson

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.4.18
    • removedInput schema / properties / caller / default
      Removed value: -"operator"
    • changedInput schema / properties / caller / enum
      Previous value: -[
-  "codex",
-  "claude",
-  "gemini",
-  "deepseek",
-  "grok",
-  "perplexity",
-  "operator"
-]New value: +[
+  "codex",
+  "claude",
+  "gemini",
+  "deepseek",
+  "grok",
+  "perplexity"
+]
    • changedInput schema / required
      Previous value: -[
-  "session_id"
-]New value: +[
+  "session_id",
+  "caller"
+]
  2. Changed1 schema field changedv4.4.9
    • addedInput schema / properties / caller
      Added value: +{
+  "default": "operator",
+  "enum": [
+    "codex",
+    "claude",
+    "gemini",
+    "deepseek",
+    "grok",
+    "perplexity",
+    "operator"
+  ],
+  "type": "string"
+}
  3. First observedv4.4.8

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. Description adds that the top-level pass reflects both enabled runtime gates and no longer emits truthfulness-only false positives, but does not define 'runtime gates' or the pass semantics, so the added value is real but incomplete.

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?

Two short sentences, no filler; the alias fact and the behavior delta are front-loaded. However, it is concise at the expense of content, so this is efficiency rather than fully informative structure.

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

Completeness1/5

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

For a tool with 6 params, no output schema, and many preflight-related siblings, the description does not cover what the check returns, what inputs mean, when to use it, or how the two gates interrelate. An agent has no basis to invoke it correctly beyond guessing compatibility with session_preflight_check.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All six parameters are undocumented in the schema (0% coverage), and the description names none of task, draft, evidence, caller, session_id, or response_format. The schema only gives structural constraints like enums/pattern, so an agent cannot know what values mean.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description identifies this as a backward-compatible alias for session_preflight_check, so an agent can map it to a known sibling, but it never states the underlying operation independently. The title adds 'Check Submission Preflights,' yet the actual checks, inputs, and decision criteria are left to inference.

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

Usage Guidelines2/5

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

No advice on when to call this vs session_preflight_check or any sibling. 'Backward-compatible alias' and 'Legacy Alias' imply the canonical sibling is preferred, but this is implicit, not an explicit routing rule.

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

Deploy Server

Other Tools