preflight_check
Read-onlyIdempotent
Get the preflight check system that protects files from accidental LLM edits.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | What to retrieve. |
Nervous System
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.1/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds context about protecting files from accidental edits, but does not disclose other behavioral traits like what happens when retrieving different actions or whether any side effects exist.
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?
The description is a single sentence with no wasted words. It is appropriately front-loaded and concise.
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?
Given the tool has one parameter with an enum and no output schema, the description is sufficiently complete. It explains the tool's protective purpose and, combined with annotations, covers the essential context for calling this read-only retrieval tool.
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?
The input schema covers 100% of parameters with descriptions, including an enum. The description adds no additional meaning beyond what the schema provides, so baseline 3 is appropriate.
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?
The description states 'Get the preflight check system' which specifies a verb and resource, but it is somewhat abstract and does not clearly differentiate how this retrieval tool differs from sibling tools like 'accountability_check' or 'security_audit'.
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 explicit guidance on when to use this tool versus alternatives. The description does not mention any prerequisites or conditions that would trigger use of preflight_check over other check tools.
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.
TDQS
A3.7/5.0
Disambiguation4/5
Most tools have clearly distinct purposes, but there is some overlap among multiple audit/check tools (e.g., accountability_check, drift_audit, security_audit). However, descriptions and naming help differentiate their specific scopes, so ambiguity is low.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_archive_safety, propagate_family_member), making them predictable and easy to understand.
Tool Count4/5
33 tools is on the high side, but the server covers a broad domain (system health, audits, propagation, session management, etc.). The count is justified by the comprehensive scope, though it may feel heavy for agents.
Completeness5/5
The tool set covers the entire lifecycle of system management: health monitoring, audits, propagation, sessions, compliance, and more. No obvious gaps for the stated purpose of a nervous system framework.